Hi all,
Based on his sustained contributions to the Sling documentation in the
last months, the Sling PPMC has decided to give Mike Müller write access
to the Sling website content wiki.
Thanks again, Mike, for your contributions and keep up the good work.
Thanks Mike and welcome!
Juanjo.
+1
but why can a commiter no longer nominate a contributor as commiter? (Since
a Committer is not always a PPMC any longer)
This might be no big difference since I think a proposal of a commiter will
be taken into account, but what is the intention of this change?
Best regards,
Dominik
On Thu,
An update draft of the Sling Community Roles and Processes as been on
the site since June 2008 [1]. This draft proposes to separate the roles
of Committers and (P)PMC members to lower the entry barrier for
committership. Additionally I added an explicit note, that regular
contributors of
BIG! Thanks!
Seams now there is someone who could clean up documentation ;)
IMHO Documentation is essential for a growing community since wrong or
incomplete documentation scares a lot of newcommers away.
Hope to read more of you soon,
Dominik
2009/5/1 Juan José Vázquez Delgado
See
http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/9/
a qualified +1 (non binding),
but only because I see problems with the management of the private list.
Committers who are not PPMC members cannot be on the private list
otherwise they will see Committer-PPMC votes, and perhaps rejections.
Further, this will mean that committers will not be
Hi,
Jukka Zitting schrieb:
Hi,
On Thu, Apr 30, 2009 at 11:07 PM, Felix Meschberger fmesc...@gmail.com
wrote:
I think it is about time to put this draft on vote and accept or drop it.
Would it be better to turn this first into a [DISCUSS] thread and
restart the vote like a week later?
Sounds good to me, any qualification I had is removed
+1 (non binding)
Ian
On 1 May 2009, at 10:57, Felix Meschberger wrote:
However, if this works ok on top level projects, then there is no
reason
why it shouldn't work for Sling.
Exactly ;-)
Hi Dominik
Dominik Süß schrieb:
+1
but why can a commiter no longer nominate a contributor as commiter? (Since
a Committer is not always a PPMC any longer)
See http://www.apache.org/foundation/how-it-works.html#roles for a
distintion between committers and (P)PMC members. In short,
Hi,
On Thu, Apr 30, 2009 at 11:07 PM, Felix Meschberger fmesc...@gmail.com wrote:
I think it is about time to put this draft on vote and accept or drop it.
Would it be better to turn this first into a [DISCUSS] thread and
restart the vote like a week later?
We had discussion on this already
Hi
Thank you all for the big welcome. I totally agree - as pointed out
in [1] - that documentation really matters to grow the community.
I agree also to do my contribution to upgrade the documentation.
But don't expect too much, it depends heavily on you mates, because
I will really need many
Hi,
On Fri, May 1, 2009 at 11:58 AM, Felix Meschberger fmesc...@gmail.com wrote:
We can leave the vote open for more time, no problem with me. And we can
continue to discuss.
OK, thanks.
+1 to the proposed changes, with a note that IMHO the division between
committers and (P)PMC members
Hi
As I try to start the huge task to upgrade the Sling documentation
there are a few questions:
1) Are there any workflows defined if I would like to restructure the existing
documentation or include some additional documentation. Or do you handle it
like code (commit then review) and I just
Hi,
Jukka Zitting schrieb:
Hi,
On Fri, May 1, 2009 at 11:58 AM, Felix Meschberger fmesc...@gmail.com wrote:
We can leave the vote open for more time, no problem with me. And we can
continue to discuss.
OK, thanks.
+1 to the proposed changes, with a note that IMHO the division between
Hi,
Mike Müller schrieb:
Hi
Thank you all for the big welcome. I totally agree - as pointed out
in [1] - that documentation really matters to grow the community.
I agree also to do my contribution to upgrade the documentation.
But don't expect too much, it depends heavily on you mates,
Hi Mike,
Mike Müller schrieb:
Hi
As I try to start the huge task to upgrade the Sling documentation
there are a few questions:
1) Are there any workflows defined if I would like to restructure the existing
documentation or include some additional documentation. Or do you handle it
like
[
https://issues.apache.org/jira/browse/SLING-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12705038#action_12705038
]
Aaron Zeckoski commented on SLING-922:
--
OK, I had some trouble generating this patch
[
https://issues.apache.org/jira/browse/SLING-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Zeckoski updated SLING-922:
-
Attachment: SLING-922.patch
binary-test-resources.zip
Everything seems to be
[
https://issues.apache.org/jira/browse/SLING-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-949.
---
Resolution: Fixed
Upgrade in Rev. 770757
Upgrade to Felix Framework release 1.6.1
See
http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/10/
Hi,
On Thu, Apr 30, 2009 at 6:59 PM, Ian Boston i...@tfd.co.uk wrote:
With JR trunk having branched 1.x off and now heading for 2.0.
What plans, if any does Sling have for moving to 2.0 and 283 support?
With my Jackrabbit release manager hat on I'd recommend that Sling
wait until Jackrabbit
21 matches
Mail list logo
