opencog-dev team mailing list archive

["David Hart" <hart@xxxxxxxxxxxx>]

A condensed version of the joining info is at
http://opencog.org/wiki/Volunteer

Finding the right balance between useful lists and list proliferation is
tricky, particularly with a project with such potentially broad appeal on
the one hand, and such high technical barriers to entry (for the core) on
the other hand (advanced AI concepts, C++ templates, etc.). It is intended
that many technical barriers will be lowered with the introduction of new
language bindings and examples/tutorials that use only subsets of the OCF
APIs; the anticipated broadening of OpenCog's user/developer coverage will
make list balance even trickier.

The opencog-dev list is intended for framework/core developers and
gravitates toward topics focused on specific ongoing and future development
(the C++, API, and tools stuff).

The difficulty with a casual developer list is that some core developers may
feel they don't want to expend the energy participating on or even
monitoring such lists. A placeholder list exists at
http://groups.google.com/group/opencog-users, although it is currently
unused and is waiting for the time when OpenCog has actual users (i.e.
developers who write MindAgents but do not modify the OpenCog Framework,
analogous to developers who write applications for Linux but who never touch
the kernel code). The opencog-users list is also intended to be a  place
where users can provide feedback to core developers, with certain posts and
threads likely cross-posted (by core developers who take notice) on
opencog-dev for core developer discussion.

-dave

On Tue, Oct 28, 2008 at 7:36 AM, Mark Waser <mwaser@xxxxxxxxxxxxx> wrote:

>  Thank you.  This was a very helpful explanation.  May I suggest that it
> be clearly posted somewhere (if it isn't already and I just missed it).
>
> What if someone doesn't wish commit access (yet) but merely wishes to
> participate on the opencog-dev mailing list (since threads are apparently
> being moved there)?
>
> - - - - -
>
> Also, at some point, hopefully sooner than later, you're going to have
> enough developers that you don't want all of them having commit
> access because coordination will turn into a nightmare even bigger than the
> current one.
> Oh, and personally, and I've done this on other projects, I would always
> prefer to work through someone who is a core member (i.e. a member of a
> small core team that is always in coordination with each other) so that I
> don't have to be in tight coordination.
>
>
>
> ----- Original Message -----
> *From:* David Hart <hart@xxxxxxxxxxxx>
> *To:* opencog@xxxxxxxxxxxxxxxx ; opencog-dev<opencog-dev@xxxxxxxxxxxxxxxxxxx>
> *Sent:* Tuesday, October 28, 2008 10:09 AM
> *Subject:* [OpenCog] joining opencog-dev
>
>  The process to join opencog-dev is simple. The team requires that
> applicants submit patches and interact constructively with the team (both
> typically via IRC) before being given commit access (e.g. the staging branch
> or other team branches). Note that anyone may make public working branches
> pulled from OpenCog code without joining the opencog-dev team!
>
> When the team member(s) you're working with think you'd be better
> requesting that your work be merged directly by Gama, rather than submitting
> patches through a team member (typically after some guidance surrounding a
> specific portion of OpenCog), they'll direct you to request an SIAI
> Individual Contributor License Agreement (typically, I'll email you a PDF
> and you'll return a scanned hand-signed version).
>
> So, the quick steps are 1) participation & cooperation 2) code 3) team
> membership
>
> -dave
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "OpenCog General & Scientific Discussion List" group.
> To post to this group, send email to opencog@xxxxxxxxxxxxxxxx
> To unsubscribe from this group, send email to
> opencog+unsubscribe@xxxxxxxxxxxxxxxx<opencog%2Bunsubscribe@xxxxxxxxxxxxxxxx>
> For more options, visit this group at
> http://groups.google.com/group/opencog?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>