|
»
»
« Return to Thread: Community-contributed modules
Re: Community-contributed modules
by Chad Kieffer-3
::
Rate this Message:
Hello,
The message I sent out was not ready to be sent. But since you
replied, here are a few comments.
On Jun 19, 2009, at 5:54 PM, rollins@... wrote:
> I wrote a module in the current gallery-contrib code tree. I have
> not followed the development of gallery 3 in depth, so I am replying
> just to you in case I am out of context.
>
> As a part-time developer, I would not want to have the ability to
> mess up the main program. I like the assurance that any mistake I
> make will have limited consequences.
>
> From a security prospective, I would recommend that write access to
> the main source code be limited to the core developers.
Only core project members have access to the core source. This will by
no means change.
> From a user perspective, I would like the user to know that the
> program obtained is indeed the one written (or authorized) by the
> core developers. The user should be aware when adding code written
> by a group other than the core developers. This will help protect
> the integrity of the project.
The approach I envision for a module directory on the Gallery Project
web site is one that is moderated first by the core team and then by
the community, much in the way that Drupal moderates their module
directory.
Module contributors develop their modules and contribute the source
via their own personal github.com account. The Gallery Project site
would create a more formal module directory. The directory would
present available modules and themes in a categorized format, allow
the community to rate modules, display download stats, etc.
It would be impossible for the core team to make any guarantees about
the quality of code or function. This responsibility would be up to
the community. Obviously, if the community found sufficient issues
with a particular module, a module should be removed if the owner/
developer is unresponsive to stated concerns.
> Quoting Chad Kieffer <chad@...>:
>
>> Hello,
>>
>> Thought I'd split out a thread devoted to community contributed
>> modules.
>>
>> Contribution policy and process
>>
>>
>>
>> Module directory
>>
>>
>>
>> Alec Myers wrote:
>>> Are you going to be able to give module developers permission to
>>> push
>>> updates to their own modules in this repo, without having to worry
>>> about
>>> whether you trust them with permission to push to the main code
>>> tree?
>>
>> Right now we don't do much with gallery3-contrib in subversion on
>> sourceforge. Ie, we don't point users at it, we don't pull from it
>> in
>> any way (like we do with Gallery 2 for downloadable plugins). So
>> basically it's just a holding area for interesting code that we don't
>> want to make part of the official package.
>>
>> I don't have a clear plan for what we do with this going forward. It
>> would be pretty easy to just add everybody as collaborators there and
>> make it a free-for-all. Or perhaps we tie it in with Romain's idea
>> for
>> a "Gallery Forge" type site? I don't know.. ideas welcome.
>>
>> ------------------------------------------------------------------------------
>> Are you an open source citizen? Join us for the Open Source Bridge
>> conference!
>> Portland, OR, June 17-19. Two days of sessions, one day of
>> unconference: $250.
>> Need another reason to go? 24-hour hacker lounge. Register today!
>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>> __[ g a l l e r y - d e v e l ]_________________________
>>
>> [ list info/archive --> http://gallery.sf.net/lists.php ]
>> [ gallery info/FAQ/download --> http://gallery.sf.net ]
>>
>
>
>
------------------------------------------------------------------------------
__[ g a l l e r y - d e v e l ]_________________________
[ list info/archive --> http://gallery.sf.net/lists.php ]
[ gallery info/FAQ/download --> http://gallery.sf.net ]
The message I sent out was not ready to be sent. But since you
replied, here are a few comments.
On Jun 19, 2009, at 5:54 PM, rollins@... wrote:
> I wrote a module in the current gallery-contrib code tree. I have
> not followed the development of gallery 3 in depth, so I am replying
> just to you in case I am out of context.
>
> As a part-time developer, I would not want to have the ability to
> mess up the main program. I like the assurance that any mistake I
> make will have limited consequences.
>
> From a security prospective, I would recommend that write access to
> the main source code be limited to the core developers.
Only core project members have access to the core source. This will by
no means change.
> From a user perspective, I would like the user to know that the
> program obtained is indeed the one written (or authorized) by the
> core developers. The user should be aware when adding code written
> by a group other than the core developers. This will help protect
> the integrity of the project.
The approach I envision for a module directory on the Gallery Project
web site is one that is moderated first by the core team and then by
the community, much in the way that Drupal moderates their module
directory.
Module contributors develop their modules and contribute the source
via their own personal github.com account. The Gallery Project site
would create a more formal module directory. The directory would
present available modules and themes in a categorized format, allow
the community to rate modules, display download stats, etc.
It would be impossible for the core team to make any guarantees about
the quality of code or function. This responsibility would be up to
the community. Obviously, if the community found sufficient issues
with a particular module, a module should be removed if the owner/
developer is unresponsive to stated concerns.
> Quoting Chad Kieffer <chad@...>:
>
>> Hello,
>>
>> Thought I'd split out a thread devoted to community contributed
>> modules.
>>
>> Contribution policy and process
>>
>>
>>
>> Module directory
>>
>>
>>
>> Alec Myers wrote:
>>> Are you going to be able to give module developers permission to
>>> push
>>> updates to their own modules in this repo, without having to worry
>>> about
>>> whether you trust them with permission to push to the main code
>>> tree?
>>
>> Right now we don't do much with gallery3-contrib in subversion on
>> sourceforge. Ie, we don't point users at it, we don't pull from it
>> in
>> any way (like we do with Gallery 2 for downloadable plugins). So
>> basically it's just a holding area for interesting code that we don't
>> want to make part of the official package.
>>
>> I don't have a clear plan for what we do with this going forward. It
>> would be pretty easy to just add everybody as collaborators there and
>> make it a free-for-all. Or perhaps we tie it in with Romain's idea
>> for
>> a "Gallery Forge" type site? I don't know.. ideas welcome.
>>
>> ------------------------------------------------------------------------------
>> Are you an open source citizen? Join us for the Open Source Bridge
>> conference!
>> Portland, OR, June 17-19. Two days of sessions, one day of
>> unconference: $250.
>> Need another reason to go? 24-hour hacker lounge. Register today!
>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>> __[ g a l l e r y - d e v e l ]_________________________
>>
>> [ list info/archive --> http://gallery.sf.net/lists.php ]
>> [ gallery info/FAQ/download --> http://gallery.sf.net ]
>>
>
>
>
------------------------------------------------------------------------------
__[ g a l l e r y - d e v e l ]_________________________
[ list info/archive --> http://gallery.sf.net/lists.php ]
[ gallery info/FAQ/download --> http://gallery.sf.net ]
« Return to Thread: Community-contributed modules
| Free embeddable forum powered by Nabble | Forum Help |
