FYI,
Since mid-2008 I've had a GitHub account which served as my public repository
for Muldis database projects.
The original account was username "muldis" and account name "Darren Duncan", and
such personal accounts were the only kinds available at the time.
More recently (a year or more ago) the concept of "organizations" came to
GitHub, and I have reorganized.
My existing 2008-era GitHub account "muldis" has been converted to be an
"organization" account, with name "Muldis Data Systems". I have also created a
brand new personal account "duncand", name "Darren Duncan"; this new one is whom
I login as and it is the "owner" of the "muldis" account. All my repositories
remain with "muldis" and so all of their urls and access paths et al still work.
The big change here, and my reason for writing you, is that now I am empowered
to add other people to the Muldis organization and thus grant them direct commit
access to the Muldis database projects. And so, a cooperative group of people
can now work directly on the projects and have their work appear in the official
place without having to make pull requests from me.
I am basically emulating a process that has been shown to work well in the Perl
community for major projects (eg, Perl, Moose, Catalyst, etc) where each project
can have a team of core committers that trust each other with direct access.
And so, if anyone has a GitHub account and wants a "commit bit" then you can
make a request. That said, I don't expect anyone to actually do this before
I've added some running code first, and its reasonably clear what is even
reasonable for you to do, but this foundation to collaborate is now there. And
people I don't know can still go the pull request route.
-- Darren Duncan
_______________________________________________
muldis-db-users mailing list
muldis-db-users@mm.darrenduncan.net
http://mm.darrenduncan.net/mailman/listinfo/muldis-db-users
