community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre Smits <pierre.sm...@gmail.com>
Subject Re: commit rights to ComDev non-community.a.o site resources
Date Sun, 15 Mar 2015 22:22:55 GMT
Why not register the solution as a component of the COMDEV project in JIRA,
and do the same as any other ASF project does when it comes to code:
register and evaluate issues, have patches registered there and have
invited committers work from there.

Best regards,

Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Sun, Mar 15, 2015 at 10:24 PM, Ulrich Stärk <uli@spielviel.de> wrote:

> Heh.
>
> When I put that sentence in the board report we didn't have projects-new
> yet.
>
> I don't see a reason why we shouldn't open up those two (or even all of
> /comdev) for all committers
> as long as changes are first discussed on our lists.
>
> What do others think?
>
> Cheers,
>
> Uli
>
> On 2015-03-14 16:38, Hervé BOUTEMY wrote:
> > Hi,
> >
> > I lately gave patches for projects-new that were not applied: it seems
> there
> > is a problem to determine who should do it (to avoid projects-new to be a
> > single-man affair).
> >
> > Then I made some investigations: in the last board report for ComDev
> [1], I
> > think I found the cause:
> > "Since artifacts produced by ComDev are usually documentation on our
> website
> > which is writable for all Apache committers, we usually do not add
> committers
> > to the ComDev project."
> >
> > Then should projects(-new).apache.org become writeable for all Apache
> > committers too? Same for reporter.apache.org?
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://whimsy.apache.org/board/minutes/Community_Development.html
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message