[Gforge-devel] submit a plug-in

[Francisco Gimeno]

Hello,

Let me comment some points:

Well... using a separate project is to avoid security problems. We SHOULDN'T 
grant access to the Gforge repository without checking that the required 
skills, trustness, experience, etc are satisfied...

Of course, it's not compulsory having a different project by each plugin, 
since they could be grouped if you have several plugins. I really don't know 
if you want to maintain the plugins or not... or to continue the development 
on gforge.org or not...

The Gplugins could be a good starting point.. I think that project was created 
for that kind of things. Currently, I'm not admin of that project, so I can't 
give you permission. Chris, Roland, what do you think about granting 
permissions on that project?

About official/unofficial plugins, I think there will not be problem to 
integrate as a First-Citizen plugin in Gforge.org, meanwhile GPL licensed, 
and tested the behaviour.

What's your unix account in gforge.org?

So, I propose you send the patches of the hooks as I told you. Then, tell us 
about your intentions of maintenance/development of those packages in the 
future ( I suppose you will want the control on gforge.org for your code, so 
we need to know your unix account in gforge.org ). With that, I think we 
could choose the best option for you ( either using gforge official tree, a 
new project, the gplugins project, etc... ). And once configured, submitting 
the code to the repositories in the easy task ;).

If you just want to Submit the plug-ins and forgive about them, then the easy 
way could send the sources to a developer ( like me, for example ). He (I) 
will review&modify&adapt&test the code, and finally will commit to 
the "official" branch if everything is OK.

I hope that I have helped you. Please, ask me all your thoughs... English is 
not my native language, so I could look like rude or unpolite... Please, 
excuse me for that. I'm willing to help you, really!

BR,
Francisco Gimeno
----------------------
> Hi,
>
> I see on Gforge that there is a project dedicated to wiki plugin and for
> gforge plug-in (http://gforge.org/projects/gplugins/)
> If I understand your answers, you propose us to create one project for
> each plug-in?.
> Now, we'll soon be able to submit two plug-ins but maybe, we'll submit
> more than two... so there'll be lots of project...
> We want to find the best way to submit our plug-ins, and of course, that
> everybody of the Gforge team can collaborate to it...
> Why can't we submit a plug-in on the gforge project? (like
> gforge-plugin-*). I suppose the reason is that our plug-ins will be
> first consider as unofficial plug-ins?
>
> Romain Valette
>
> Tim Perdue wrote:
> > Romain Valette wrote:
> >> Hi all,
> >>
> >> I'm working for Bull S.A in France.
> >> We use Gforge to manage some of our projects and we added
> >> customizations on it for the needs of Bull.
> >> These were made by a development in "plug-in" like it is discribed in
> >> your documentation.
> >> So I participated in the development of plug-in such as the
> >> cvs-versionning for submitted documentation or for submitted files.
> >>
> >> How can we submit them? I've read your documentation named
> >> "contribution guide" but there is no way to submit a plug-in... Maybe
> >> I miss it....
> >> And of course, to use these plug-ins, We have to add some "hooks" in
> >> Gforge source code so We also have to commit these files...
> >
> > You can tar it up and submit it to the patch tracker. We can also
> > create a separate project for it if you plan to continue working on it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://svr1.gforge.org/pipermail/gforge-devel/attachments/20060622/7f11a176/attachment.bin