Last week, Keith and I discussed this, and he said he could possibly
get a very quick Drupal site set up for PHP user groups. We don't have
to worry yet about all the other details we've been discussing. I
agree with him that the important thing for right now is to get
something set up.
So, two points:
1) Keith, you're setting this up, right?
2) Wherever it's hosted, let's set it up under the phpgroups.org
domain for now. Let me know the IP, and I'll adjust the DNS to point
to it.
Once we get something up and running for the groups, then we should
have discussions on how we'll maintain it moving forward (VCS, etc.)
On a completely separate topic, Dragoonis was asking about the
phpcommunity.org website. Let's hold off on that for now. We're still
working through some "PHP Community" (the organization) organizational
details.
On Wed, Dec 9, 2009 at 14:48, Ben Ramsey <b...@benramsey.com> wrote:
> Last week, Keith and I discussed this, and he said he could possibly
> get a very quick Drupal site set up for PHP user groups. We don't have
> to worry yet about all the other details we've been discussing. I
> agree with him that the important thing for right now is to get
> something set up.
> So, two points:
> 1) Keith, you're setting this up, right?
> 2) Wherever it's hosted, let's set it up under the phpgroups.org
> domain for now. Let me know the IP, and I'll adjust the DNS to point
> to it.
> Once we get something up and running for the groups, then we should
> have discussions on how we'll maintain it moving forward (VCS, etc.)
> On a completely separate topic, Dragoonis was asking about the
> phpcommunity.org website. Let's hold off on that for now. We're still
> working through some "PHP Community" (the organization) organizational
> details.
> -Ben
> --
> You received this message because you are subscribed to the Google Groups
> "PHP Community Projects" group.
> To post to this group, send email to phpc-projects@googlegroups.com.
> To unsubscribe from this group, send email to
> phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/phpc-projects?hl=en.
Rafael Dohms wrote:
> As i said at that time, i agree with the drupal install for now.. get it > out there.
> If case comes to case we can then replace with custom systems when they > are ready.
Yes, please start bugging me on Friday if I don't have something online. The UI isn't going to be fantastic, but we can start collecting data and someone can think on the UI. :)
Nice! Looking forward to seeing this up! I've got a substantial amount of
drupal experience and will be happy to help (also have a server if we need
space for anything).
Aaron
On Wed, Dec 9, 2009 at 11:58 AM, D. Keith Casey Jr. <ke...@caseysoftware.com
> wrote:
> Rafael Dohms wrote:
> > As i said at that time, i agree with the drupal install for now.. get it
> > out there.
> > If case comes to case we can then replace with custom systems when they
> > are ready.
> Yes, please start bugging me on Friday if I don't have something online.
> The
> UI isn't going to be fantastic, but we can start collecting data and
> someone
> can think on the UI. :)
> You received this message because you are subscribed to the Google Groups
> "PHP Community Projects" group.
> To post to this group, send email to phpc-projects@googlegroups.com.
> To unsubscribe from this group, send email to
> phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/phpc-projects?hl=en.
On Dec 9, 11:58 am, "D. Keith Casey Jr." <ke...@caseysoftware.com> wrote:
> Yes, please start bugging me on Friday if I don't have something online. The > UI isn't going to be fantastic, but we can start collecting data and someone > can think on the UI. :)
Ben Ramsey wrote: > On Dec 9, 11:58 am, "D. Keith Casey Jr." <ke...@caseysoftware.com> > wrote: >> Yes, please start bugging me on Friday if I don't have something online. The >> UI isn't going to be fantastic, but we can start collecting data and someone >> can think on the UI. :)
> wrote: > Ben Ramsey wrote: > > On Dec 9, 11:58 am, "D. Keith Casey Jr." <ke...@caseysoftware.com> > > wrote: > >> Yes, please start bugging me on Friday if I don't have something online. > The > >> UI isn't going to be fantastic, but we can start collecting data and > someone > >> can think on the UI. :)
> Ha, no. I'm rolling some stuff out this week though.
> It will be interesting to see what they do with that one. They don't have a > community guy and it would have made much more sense as part of DevZone...
> kc
> --
> You received this message because you are subscribed to the Google Groups > "PHP Community Projects" group. > To post to this group, send email to phpc-projects@googlegroups.com. > To unsubscribe from this group, send email to > phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> > . > For more options, visit this group at > http://groups.google.com/group/phpc-projects?hl=en.
my opinion is that having our UG name in Zends site... never hurts.. as they do reach a lot of people who are not "community" oriented yet.
this will prob. run the same lines as others and become outdated and such, which is why our direcotry will have all the diferent validation and expiration stuff.
but hey... go zend... but please link to our directory onc
> Personally, I'm under the impression that a resource about the community > should be run by people, you know, in he community *cough*
> -chris
> On Mon, Dec 28, 2009 at 3:45 PM, D. Keith Casey Jr. < > ke...@caseysoftware.com> wrote:
>> Ben Ramsey wrote: >> > On Dec 9, 11:58 am, "D. Keith Casey Jr." <ke...@caseysoftware.com> >> > wrote: >> >> Yes, please start bugging me on Friday if I don't have something >> online. The >> >> UI isn't going to be fantastic, but we can start collecting data and >> someone >> >> can think on the UI. :)
>> Ha, no. I'm rolling some stuff out this week though.
>> It will be interesting to see what they do with that one. They don't have >> a >> community guy and it would have made much more sense as part of DevZone...
>> kc
>> --
>> You received this message because you are subscribed to the Google Groups >> "PHP Community Projects" group. >> To post to this group, send email to phpc-projects@googlegroups.com. >> To unsubscribe from this group, send email to >> phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/phpc-projects?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "PHP Community Projects" group. > To post to this group, send email to phpc-projects@googlegroups.com. > To unsubscribe from this group, send email to > phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> > . > For more options, visit this group at > http://groups.google.com/group/phpc-projects?hl=en.
On Mon, Dec 28, 2009 at 21:14, Rafael Dohms <rdo...@gmail.com> wrote: > my opinion is that having our UG name in Zends site... never hurts.. as > they do reach a lot of people who are not "community" oriented yet.
> this will prob. run the same lines as others and become outdated and such, > which is why our direcotry will have all the diferent validation and > expiration stuff.
> but hey... go zend... but please link to our directory onc
> On Mon, Dec 28, 2009 at 20:03, Chris Cornutt <eny...@phpdeveloper.org>wrote:
>> Personally, I'm under the impression that a resource about the community >> should be run by people, you know, in he community *cough*
>> -chris
>> On Mon, Dec 28, 2009 at 3:45 PM, D. Keith Casey Jr. < >> ke...@caseysoftware.com> wrote:
>>> Ben Ramsey wrote: >>> > On Dec 9, 11:58 am, "D. Keith Casey Jr." <ke...@caseysoftware.com> >>> > wrote: >>> >> Yes, please start bugging me on Friday if I don't have something >>> online. The >>> >> UI isn't going to be fantastic, but we can start collecting data and >>> someone >>> >> can think on the UI. :)
>>> Ha, no. I'm rolling some stuff out this week though.
>>> It will be interesting to see what they do with that one. They don't have >>> a >>> community guy and it would have made much more sense as part of >>> DevZone...
>>> kc
>>> --
>>> You received this message because you are subscribed to the Google Groups >>> "PHP Community Projects" group. >>> To post to this group, send email to phpc-projects@googlegroups.com. >>> To unsubscribe from this group, send email to >>> phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/phpc-projects?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "PHP Community Projects" group. >> To post to this group, send email to phpc-projects@googlegroups.com. >> To unsubscribe from this group, send email to >> phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/phpc-projects?hl=en.
I agree that it should be run by a community person, but I also agree that free publicity never hurt anyone :) Anything that gets our name out there to others is ok with me.
Maybe we should have told Zend that if they'd have waited a while longer, we would have had an open API they could have used :D
> On Mon, Dec 28, 2009 at 21:14, Rafael Dohms <rdo...@gmail.com> wrote:
>> my opinion is that having our UG name in Zends site... never hurts.. as >> they do reach a lot of people who are not "community" oriented yet.
>> this will prob. run the same lines as others and become outdated and such, >> which is why our direcotry will have all the diferent validation and >> expiration stuff.
>> but hey... go zend... but please link to our directory onc
>> On Mon, Dec 28, 2009 at 20:03, Chris Cornutt <eny...@phpdeveloper.org>wrote:
>>> Personally, I'm under the impression that a resource about the community >>> should be run by people, you know, in he community *cough*
>>> -chris
>>> On Mon, Dec 28, 2009 at 3:45 PM, D. Keith Casey Jr. < >>> ke...@caseysoftware.com> wrote:
>>>> Ben Ramsey wrote: >>>> > On Dec 9, 11:58 am, "D. Keith Casey Jr." <ke...@caseysoftware.com> >>>> > wrote: >>>> >> Yes, please start bugging me on Friday if I don't have something >>>> online. The >>>> >> UI isn't going to be fantastic, but we can start collecting data and >>>> someone >>>> >> can think on the UI. :)
>>>> Ha, no. I'm rolling some stuff out this week though.
>>>> It will be interesting to see what they do with that one. They don't >>>> have a >>>> community guy and it would have made much more sense as part of >>>> DevZone...
>>>> kc
>>>> --
>>>> You received this message because you are subscribed to the Google >>>> Groups "PHP Community Projects" group. >>>> To post to this group, send email to phpc-projects@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> >>>> . >>>> For more options, visit this group at >>>> http://groups.google.com/group/phpc-projects?hl=en.
>>> -- >>> You received this message because you are subscribed to the Google Groups >>> "PHP Community Projects" group. >>> To post to this group, send email to phpc-projects@googlegroups.com. >>> To unsubscribe from this group, send email to >>> phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/phpc-projects?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "PHP Community Projects" group. > To post to this group, send email to phpc-projects@googlegroups.com. > To unsubscribe from this group, send email to > phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> > . > For more options, visit this group at > http://groups.google.com/group/phpc-projects?hl=en.
What functionality would you like to have that API implemented ? Personally I believe that Zend has made a good approach by calling all "known" ug admins to list their user group, implying they would inform their network of ug admins about the functionality.
Seems to me it would work better then again another API out there.
> On 12/28/09 7:12 PM, Elizabeth Naramore wrote: >> Maybe we should have told Zend that if they'd have waited a while >> longer, we would have had an open API they could have used :D
> Yeah, but the problem with this is that it could be 3 months, 6 months, > a year, or 5 years before we build that. ;-)
> I hope we can get something up in 2010, though. 2010 is already shaping > up to be a big year for strengthening the PHP community.
> You received this message because you are subscribed to the Google Groups "PHP Community Projects" group. > To post to this group, send email to phpc-projects@googlegroups.com. > To unsubscribe from this group, send email to phpc-projects+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/phpc-projects?hl=en.
Ideally, it would be nice to be able to add my group (or make changes as leadership changes, meeting time or location changes, etc.) in *one* place and have that be the location that other sites feed from.
Right now, if something major changes with my group, I have to make that change to: -php.net -phpgroups.org -phpusergroups.org -our listing on publisher sites, like packt.com, apress.com, pearson.com, oreilly, etc. -now zend
This is in addition to the sites we already have to keep up with, including: -the oink-pug main site -our linked in group -our facebook group -our twitter account -our meetup group -our listing in the local techlife site (which lists local tech events) -our listing in the local circuit site (which also lists local tech events)
(for the record, WE ARE NOT CHANGING ANYTHING. EVER. :) )
Additionally, the Zend site does not allow me to put in much information about my group. I understand the point is to be a high-level reference for people, and ultimately point users to the individual sites for more info, but I'd like to be able to give more info there.
Is there a PHP User group API already floating around? If so, my mistake. And really my point was more tongue-in-cheek than anything, as it's certainly something we could offer in the future, but not something we have put together yet (as Ramsey mentioned).
Cheers! E.
On Tue, Dec 29, 2009 at 7:21 AM, Michelangelo van Dam <drago...@gmail.com>wrote:
> What functionality would you like to have that API implemented ? Personally > I believe that Zend has made a good approach by calling all "known" ug > admins to list their user group, implying they would inform their network of > ug admins about the functionality.
> Seems to me it would work better then again another API out there.
> My $ 0.02,
> Michelangelo
> On 29 Dec 2009, at 02:15, Ben Ramsey wrote:
> > On 12/28/09 7:12 PM, Elizabeth Naramore wrote: > >> Maybe we should have told Zend that if they'd have waited a while > >> longer, we would have had an open API they could have used :D
> > Yeah, but the problem with this is that it could be 3 months, 6 months, > > a year, or 5 years before we build that. ;-)
> > I hope we can get something up in 2010, though. 2010 is already shaping > > up to be a big year for strengthening the PHP community.
> > You received this message because you are subscribed to the Google Groups > "PHP Community Projects" group. > > To post to this group, send email to phpc-projects@googlegroups.com. > > To unsubscribe from this group, send email to > phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> > . > > For more options, visit this group at > http://groups.google.com/group/phpc-projects?hl=en.
> --
> You received this message because you are subscribed to the Google Groups > "PHP Community Projects" group. > To post to this group, send email to phpc-projects@googlegroups.com. > To unsubscribe from this group, send email to > phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> > . > For more options, visit this group at > http://groups.google.com/group/phpc-projects?hl=en.
> Is there a PHP User group API already floating around? If so, my > mistake. And really my point was more tongue-in-cheek than anything, as > it's certainly something we could offer in the future, but not something > we have put together yet (as Ramsey mentioned).
Man, I hate you guys.
Luckily, I'm already working with content synchronization in Drupal, so I already have code that will create an XML structure outputting the info from a given content item (group). Regardless, I'm going to get it online first... and then turn that on and encourage Zend, php.net, etc, etc to subscribe to *that*.
>> Is there a PHP User group API already floating around? If so, my >> mistake. And really my point was more tongue-in-cheek than anything, as >> it's certainly something we could offer in the future, but not something >> we have put together yet (as Ramsey mentioned).
> Man, I hate you guys.
> Luckily, I'm already working with content synchronization in Drupal, so I > already have code that will create an XML structure outputting the info from a > given content item (group). Regardless, I'm going to get it online first... > and then turn that on and encourage Zend, php.net, etc, etc to subscribe to > *that*.
> What is the url where this will go?
Whatever you want it to be. I can make it the default for the phpgroups.org domain, or we can put it at an interim subdomain for now.
What does everyone else think?
Also, since this discussion mainly involves the user groups for now, maybe we should take this over to the ug-admins list on lists.php.net? (What I hate about the PHP.net mailing list is that I have no idea who is on it, but I love the fact that it's within the php.net domain.)
Finally, circling back to Elizabeth's list of sites that user groups must constantly update when posting meetings and information, this isn't just a problem PHP user groups have. It's a problem all groups and organizations of this type have. I've been thinking for a while that it would be good to develop a platform for user groups that would tie in to the APIs for all of these services so that user group organizers would only need to log in to one place and update them all at the same time. This is out of scope for us, but it's definitely something to think about, and maybe a group of us can eventually build that service (possibly with some sponsorship help). :-)
god damn i wish i had more free time to code all the ideas i'm getting.
I agree this is a major "i want" for most groups .. i think we should start jotting down a structure for what our *ideal* directory would be... put it up on a mantis or whatnot.. setup a github account and let people start contributing with what they can.. as long as we have a common goal and structure laid out.. we can code parallely and each of us contribute what time we have...
On Tue, Dec 29, 2009 at 15:09, Ben Ramsey <b...@benramsey.com> wrote: > On 12/29/09 11:04 AM, D. Keith Casey Jr. wrote:
> >> Is there a PHP User group API already floating around? If so, my > >> mistake. And really my point was more tongue-in-cheek than anything, as > >> it's certainly something we could offer in the future, but not something > >> we have put together yet (as Ramsey mentioned).
> > Man, I hate you guys.
> > Luckily, I'm already working with content synchronization in Drupal, so I > > already have code that will create an XML structure outputting the info > from a > > given content item (group). Regardless, I'm going to get it online > first... > > and then turn that on and encourage Zend, php.net, etc, etc to subscribe > to > > *that*.
> > What is the url where this will go?
> Whatever you want it to be. I can make it the default for the > phpgroups.org domain, or we can put it at an interim subdomain for now.
> What does everyone else think?
> Also, since this discussion mainly involves the user groups for now, > maybe we should take this over to the ug-admins list on lists.php.net? > (What I hate about the PHP.net mailing list is that I have no idea who > is on it, but I love the fact that it's within the php.net domain.)
> Finally, circling back to Elizabeth's list of sites that user groups > must constantly update when posting meetings and information, this isn't > just a problem PHP user groups have. It's a problem all groups and > organizations of this type have. I've been thinking for a while that it > would be good to develop a platform for user groups that would tie in to > the APIs for all of these services so that user group organizers would > only need to log in to one place and update them all at the same time. > This is out of scope for us, but it's definitely something to think > about, and maybe a group of us can eventually build that service > (possibly with some sponsorship help). :-)
> You received this message because you are subscribed to the Google Groups > "PHP Community Projects" group. > To post to this group, send email to phpc-projects@googlegroups.com. > To unsubscribe from this group, send email to > phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> > . > For more options, visit this group at > http://groups.google.com/group/phpc-projects?hl=en.
Rafael Dohms wrote: > I agree this is a major "i want" for most groups .. i think we should > start jotting down a structure for what our *ideal* directory would > be... put it up on a mantis or whatnot.. setup a github account and let > people start contributing with what they can.. as long as we have a > common goal and structure laid out.. we can code parallely and each of > us contribute what time we have...
The big problem is that not all of those sites have APIs. For the ones that do, quite often you're *extremely* limited in what you can do... normally a lot of read-only stuff.
I spent about 9 months of my life with a team of 7 trying to do this - and a number of other things, but this fit part of it - and it's a horrible pain. Whenever any site changes its API in the slightest, you have to change all of it once again... you're always reacting to everything/everyone else, often without warning. :(
In terms of building a custom app for it. I'm still opposed. I'd rather work within an existing system (Drupal, WP, SugarCRM, Habari, whatever) and do cool things like "find the nearest user group by geolocating your IP" as opposed to building *yet another* log in system with a "forgot password" link, etc.
And of course, rolling out another custom app means that someone has to maintain it once you're gone. And despite rumors to the contrary, I'll take upgrading any of the above systems over a PHP upgrade *any* day.
No objection in building on top of something else.
The code i shared for the ugdirectory i started uses wordpress as its login/backend stuff.. I only built the actual UG stuff.. with a login module which we can tie into drupal, wp, or whatever the underlying thing is...
But is we wan a full blown api and geo all kinds of cool things... building everything customized inside drupal and etc.. is extremelly painful in my experience.
> Rafael Dohms wrote: > > I agree this is a major "i want" for most groups .. i think we should > > start jotting down a structure for what our *ideal* directory would > > be... put it up on a mantis or whatnot.. setup a github account and let > > people start contributing with what they can.. as long as we have a > > common goal and structure laid out.. we can code parallely and each of > > us contribute what time we have...
> The big problem is that not all of those sites have APIs. For the ones > that > do, quite often you're *extremely* limited in what you can do... normally a > lot of read-only stuff.
> I spent about 9 months of my life with a team of 7 trying to do this - and > a > number of other things, but this fit part of it - and it's a horrible pain. > Whenever any site changes its API in the slightest, you have to change all > of > it once again... you're always reacting to everything/everyone else, often > without warning. :(
> In terms of building a custom app for it. I'm still opposed. I'd rather > work > within an existing system (Drupal, WP, SugarCRM, Habari, whatever) and do > cool > things like "find the nearest user group by geolocating your IP" as opposed > to > building *yet another* log in system with a "forgot password" link, etc.
> And of course, rolling out another custom app means that someone has to > maintain it once you're gone. And despite rumors to the contrary, I'll > take > upgrading any of the above systems over a PHP upgrade *any* day.
> kc
> --
> You received this message because you are subscribed to the Google Groups > "PHP Community Projects" group. > To post to this group, send email to phpc-projects@googlegroups.com. > To unsubscribe from this group, send email to > phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> > . > For more options, visit this group at > http://groups.google.com/group/phpc-projects?hl=en.
On Tue, Dec 29, 2009 at 3:08 PM, D. Keith Casey Jr. <ke...@caseysoftware.com
> wrote: > The big problem is that not all of those sites have APIs. For the ones > that > do, quite often you're *extremely* limited in what you can do... normally a > lot of read-only stuff.
> I spent about 9 months of my life with a team of 7 trying to do this - and > a > number of other things, but this fit part of it - and it's a horrible pain. > Whenever any site changes its API in the slightest, you have to change all > of > it once again... you're always reacting to everything/everyone else, often > without warning. :(
I'm not sure about the others, but I was suggesting *we* be the central repository for that info, provide the API, and let others grab it from us. That being said, you're absolutely right when you say it's one more thing for someone to code/upgrade/maintain/worry about. :)
> In terms of building a custom app for it. I'm still opposed. I'd rather work > within an existing system (Drupal, WP, SugarCRM, Habari, whatever)
I don't think we're arguing the merits of developing a custom app vs. using an existing system here. All I said was that I would be nice to provide a central service that any user group/organization could use to log in to and update all of these services at the same time. The technology behind it is immaterial at this point since we don't even know what the service would be/provide or even if it's something this group would even be responsible for. :-)
Probably the best solution would be to could create a couple extensions to the XMPP protocol to handle that - we could then set up PHPC jabber server ( xmpp.phpcommunity.com)? which would use Presence to ensure that all the UG directories are kept in sync.
Or we could just instruct the UG organizers to update the information in a couple different places.
Aaron
On Tue, Dec 29, 2009 at 10:46 AM, Elizabeth Naramore <
elizabeth.naram...@gmail.com> wrote: > Ideally, it would be nice to be able to add my group (or make changes as > leadership changes, meeting time or location changes, etc.) in *one* place > and have that be the location that other sites feed from.
> Right now, if something major changes with my group, I have to make that > change to: > -php.net > -phpgroups.org > -phpusergroups.org > -our listing on publisher sites, like packt.com, apress.com, pearson.com, > oreilly, etc. > -now zend
> This is in addition to the sites we already have to keep up with, > including: > -the oink-pug main site > -our linked in group > -our facebook group > -our twitter account > -our meetup group > -our listing in the local techlife site (which lists local tech events) > -our listing in the local circuit site (which also lists local tech events)
> (for the record, WE ARE NOT CHANGING ANYTHING. EVER. :) )
> Additionally, the Zend site does not allow me to put in much information > about my group. I understand the point is to be a high-level reference for > people, and ultimately point users to the individual sites for more info, > but I'd like to be able to give more info there.
> Is there a PHP User group API already floating around? If so, my mistake. > And really my point was more tongue-in-cheek than anything, as it's > certainly something we could offer in the future, but not something we have > put together yet (as Ramsey mentioned).
> Cheers! > E.
> On Tue, Dec 29, 2009 at 7:21 AM, Michelangelo van Dam <drago...@gmail.com>wrote:
>> Elizabeth,
>> What functionality would you like to have that API implemented ? >> Personally I believe that Zend has made a good approach by calling all >> "known" ug admins to list their user group, implying they would inform their >> network of ug admins about the functionality.
>> Seems to me it would work better then again another API out there.
>> My $ 0.02,
>> Michelangelo
>> On 29 Dec 2009, at 02:15, Ben Ramsey wrote:
>> > On 12/28/09 7:12 PM, Elizabeth Naramore wrote: >> >> Maybe we should have told Zend that if they'd have waited a while >> >> longer, we would have had an open API they could have used :D
>> > Yeah, but the problem with this is that it could be 3 months, 6 months, >> > a year, or 5 years before we build that. ;-)
>> > I hope we can get something up in 2010, though. 2010 is already shaping >> > up to be a big year for strengthening the PHP community.
>> > You received this message because you are subscribed to the Google >> Groups "PHP Community Projects" group. >> > To post to this group, send email to phpc-projects@googlegroups.com. >> > To unsubscribe from this group, send email to >> phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> >> . >> > For more options, visit this group at >> http://groups.google.com/group/phpc-projects?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups >> "PHP Community Projects" group. >> To post to this group, send email to phpc-projects@googlegroups.com. >> To unsubscribe from this group, send email to >> phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/phpc-projects?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "PHP Community Projects" group. > To post to this group, send email to phpc-projects@googlegroups.com. > To unsubscribe from this group, send email to > phpc-projects+unsubscribe@googlegroups.com<phpc-projects%2Bunsubscribe@goog legroups.com> > . > For more options, visit this group at > http://groups.google.com/group/phpc-projects?hl=en.
Elizabeth Naramore wrote: > I'm not sure about the others, but I was suggesting *we* be the central > repository for that info, provide the API, and let others grab it from > us. That being said, you're absolutely right when you say it's one more > thing for someone to code/upgrade/maintain/worry about. :)
IMHO, that's an even harder effort.
We would have to convince each of those groups that it's valuable to integrate with us. While at the same time, there are a dozen groups just like us trying to convince those companies that *they're* the ones that should be integrated. I think it's a great idea, but it's a game of convincing them that they need us.
...and realistically, Meetup or Ning could replace us in a weekend.
Personally, I'd rather drink my spiked eggnog or raise a toast to all of us for 2010. ;)
> Elizabeth Naramore wrote: >> I'm not sure about the others, but I was suggesting *we* be the central >> repository for that info, provide the API, and let others grab it from >> us. That being said, you're absolutely right when you say it's one more >> thing for someone to code/upgrade/maintain/worry about. :)
> IMHO, that's an even harder effort.
I don't think this is a feasible problem for us to solve. It's someone else's problem. I was just suggesting that perhaps some people in this group might be up for the challenge. I'm not suggesting that this be our focus, though.
> Personally, I'd rather drink my spiked eggnog or raise a toast to all of us > for 2010. ;)
