Re: Welcome Mike Mueller as Documentation Committer
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.
Re: [VOTE] Update to Community Roles and Processes
+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, Apr 30, 2009 at 11:07 PM, Felix Meschberger fmesc...@gmail.comwrote: Hi all, 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 documentation may be elected as Committers just like regular contributors of code. I think it is about time to put this draft on vote and accept or drop it. So lets start a vote on this the current draft for the Sling Community Roles and Processes [1]: [ ] +1 Yes [ ] -1 No, because ... This is a majority vote running until Tuesday, 5. May 2009 (due to long weekend in large parts of Europe). Thanks and Regards Felix [1] http://cwiki.apache.org/SLINGxSITE/apache-sling-community-roles-and-processes.html
Re: [VOTE] Update to Community Roles and Processes
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 documentation may be elected as Committers just like regular contributors of code. I think it is about time to put this draft on vote and accept or drop it. So lets start a vote on this the current draft for the Sling Community Roles and Processes [1]: [ ] +1 Yes [ ] -1 No, because ... +1 BR, Juanjo.
Re: Welcome Mike Mueller as Documentation Committer
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 juanjo.vazq...@gmail.com 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.
Hudson build is still unstable: sling-contrib- 1.5 » Apache Sling Launchpad Contrib Testing #9
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/9/
Re: [VOTE] Update to Community Roles and Processes
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 able to cast votes, even non binding, on elections of new committers. However, if this works ok on top level projects, then there is no reason why it shouldn't work for Sling. Ian On 30 Apr 2009, at 22:07, Felix Meschberger wrote: Hi all, 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 documentation may be elected as Committers just like regular contributors of code. I think it is about time to put this draft on vote and accept or drop it. So lets start a vote on this the current draft for the Sling Community Roles and Processes [1]: [ ] +1 Yes [ ] -1 No, because ... This is a majority vote running until Tuesday, 5. May 2009 (due to long weekend in large parts of Europe). Thanks and Regards Felix [1] http://cwiki.apache.org/SLINGxSITE/apache-sling-community-roles-and-processes.html
Re: [VOTE] Update to Community Roles and Processes
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? We can leave the vote open for more time, no problem with me. And we can continue to discuss. Regards Felix We had discussion on this already last summer, but now that I look back to it, it happened on sling-priv...@. It would be good to get feedback and consensus also from the larger community (who are most affected by the policy change!) before nailing it down. BR, Jukka Zitting
Re: [VOTE] Update to Community Roles and Processes
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 ;-)
Re: [VOTE] Update to Community Roles and Processes
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, committers just have write access to SVN. PMC members (for graduated project, for incubator projects it is the PPMC in cooperation with the Incubator PMC) control the project. 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? Comittership discussions generally take place amongst the (P)PMC on the private list. Of course a committer may send a proposal to the private list. But yes, a committer is excluded from the discussion. The goal of this proposal is to lower the entry barrier to grow the committer community: Up to now all committers are also (P)PMC members, which raises the barrier. For (P)PMC members we generally expect longer term committal to the project than from committers. Of course, nobody prevents us from voting in a person directly into the (P)PMC and for committership at the same time. But this is not automatic any more. Regards Felix Best regards, Dominik On Thu, Apr 30, 2009 at 11:07 PM, Felix Meschberger fmesc...@gmail.comwrote: Hi all, 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 documentation may be elected as Committers just like regular contributors of code. I think it is about time to put this draft on vote and accept or drop it. So lets start a vote on this the current draft for the Sling Community Roles and Processes [1]: [ ] +1 Yes [ ] -1 No, because ... This is a majority vote running until Tuesday, 5. May 2009 (due to long weekend in large parts of Europe). Thanks and Regards Felix [1] http://cwiki.apache.org/SLINGxSITE/apache-sling-community-roles-and-processes.html
Re: [VOTE] Update to Community Roles and Processes
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 last summer, but now that I look back to it, it happened on sling-priv...@. It would be good to get feedback and consensus also from the larger community (who are most affected by the policy change!) before nailing it down. BR, Jukka Zitting
AW: Welcome Mike Mueller as Documentation Committer
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 inputs to get deep into the details and do some documentation. So expect more questions from my side on the mailing list ;-) best regards mike [1] http://markmail.org/thread/4tey2eoeh7jzkbkm 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 juanjo.vazq...@gmail.com 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.
Re: [VOTE] Update to Community Roles and Processes
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 should only be used to lower the barrier for committership, not to raise the barrier for (P)PMC membership. BR, Jukka Zitting
Upgrading the Sling Site, a few questions
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 make a note to the mailing list after changing something on the Sling site? 2) Is it a good idea to publish documentation which is probably not complete or maybe incorrect in the public wiki for reviewing and transfer it to the Sling site later? 3) Does someone has drafts of documentation which cannot be published but would be a good starting position to describe a feature or functionality? If yes please send it directly to me. I try to start from the point of view of a newbie which is interested in Sling. So I will start to update the following - getting/builing source, IDE setup, debugging, installing, tools (Eclipse, JCR explorer) - description of the core engine (request resolution) - description of the main bundles (does someone has any documentation about individual bundles?) best regards mike
Re: [VOTE] Update to Community Roles and Processes
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 committers and (P)PMC members should only be used to lower the barrier for committership, not to raise the barrier for (P)PMC membership. That's definitely the goal ! Regards Felix BR, Jukka Zitting
Re: AW: Welcome Mike Mueller as Documentation Committer
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, because I will really need many inputs to get deep into the details and do some documentation. So expect more questions from my side on the mailing list ;-) Sure, we try to answer as good as we can ! Regards Felix best regards mike [1] http://markmail.org/thread/4tey2eoeh7jzkbkm 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 juanjo.vazq...@gmail.com 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.
Re: Upgrading the Sling Site, a few questions
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 code (commit then review) and I just make a note to the mailing list after changing something on the Sling site? We don't have any written workflow. We pretty much just update as we see fit. The only concern I try to cope with is that we keep the URLs as much as possible (if it ain't possible, it ain't). But using Confluence this is less hard than it sounds: all pages reside in a single directory in the filesystem where the name is derived from the page name. So, as long as the page name is not changed, the URL is not changed. 2) Is it a good idea to publish documentation which is probably not complete or maybe incorrect in the public wiki for reviewing and transfer it to the Sling site later? I don't think that there is an absolute answer to this. Generally, I would thinkg putting the documentation on site is just as good and you may mark missing portions as TODO or such... 3) Does someone has drafts of documentation which cannot be published but would be a good starting position to describe a feature or functionality? If yes please send it directly to me. I try to start from the point of view of a newbie which is interested in Sling. So I will start to update the following - getting/builing source, IDE setup, debugging, installing, tools (Eclipse, JCR explorer) - description of the core engine (request resolution) - description of the main bundles (does someone has any documentation about individual bundles?) Sounds like a very good plan to me. Thanks and Regards Felix
[jira] Commented: (SLING-922) Load modules on startup from an external directory
[
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 file so my apologies if it ends up
being a little tricky to apply the patch. I have attached a zip which has the
binary pieces used in the test. The remaining stuff should be visible in the
patch file. So apply the patch and then extract the binary-test-resources into
the sling trunk and then the build should be fine.
Load modules on startup from an external directory
--
Key: SLING-922
URL: https://issues.apache.org/jira/browse/SLING-922
Project: Sling
Issue Type: New Feature
Components: Launchpad, Launchpad Launcher
Reporter: Aaron Zeckoski
Assignee: Felix Meschberger
Original Estimate: 72h
Remaining Estimate: 72h
Need a way to install and start bundles automatically from an external
directory (sling home) on startup. The ideas below are from the list.
--
I would like to be able to setup sling to start with a bunch of
installed bundles when it first is started. It seems like there are a
couple way to do this that I have found but neither is ideal:
1) Rebuild sling from source with the extra bundles in the launcher
pom (this seems to create a bunch of resources/# folders with bundles
in them)
2) Configure all bundles in the sling.properties file (this requires
the bundles to be in an accessible obr)
http://incubator.apache.org/sling/site/provisioning-and-startup.html
I would like to ideally do something in between like so:
Get a binary copy of the sling jar
Create a folder with sub-folders like /1 /10 /15
Put my bundles in the various subfolders
Configure sling.properties to point to the folder
Start sling and have all bundles in the sub-folders installed and started
- Aaron Zeckoski
===
Currently, as you say in (1), the BootstrapInstaller of the Sling
launchpad looks into its own resources enclosed in the JAR or WAR file
for bundles to install on startup.
How about extending this mechanism like this:
- Copy all bundles from enclosed resources to
${sling.home}/startup. This gives something like
${sling.home}/startup/0, /1, /10, /15, ...
Existing files are only replaced if the files
enclosed in the Sling launchpad jar/war file are
newer.
- Scan ${sling.home}/startup for bundles to install
in the same way as today the enclosed resources
are scanned directly.
So you could place your bundles in that structure and get them installed
at the requested start level (0 being default bundle start level).
A nice side effect of this is, that you can quickly see, which bundles
have been installed at all.
- Felix
=
I like this, and agree that this should replace the current mechanism.
How about adding a sling.properties option to completely ignore the
bundles that come from the Sling jar/war file? Might make it easier to
have precise control on what's installed.
-Bertrand
=
Maybe worth it to make this optional or controllable via a property in the
sling properties.
- Aaron Zeckoski
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-922) Load modules on startup from an external directory
[
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 working on my machine so I think this is ready to go.
Please let me know if there are any issues and I will generate a new patch.
Load modules on startup from an external directory
--
Key: SLING-922
URL: https://issues.apache.org/jira/browse/SLING-922
Project: Sling
Issue Type: New Feature
Components: Launchpad, Launchpad Launcher
Reporter: Aaron Zeckoski
Assignee: Felix Meschberger
Attachments: binary-test-resources.zip, SLING-922.patch
Original Estimate: 72h
Remaining Estimate: 72h
Need a way to install and start bundles automatically from an external
directory (sling home) on startup. The ideas below are from the list.
--
I would like to be able to setup sling to start with a bunch of
installed bundles when it first is started. It seems like there are a
couple way to do this that I have found but neither is ideal:
1) Rebuild sling from source with the extra bundles in the launcher
pom (this seems to create a bunch of resources/# folders with bundles
in them)
2) Configure all bundles in the sling.properties file (this requires
the bundles to be in an accessible obr)
http://incubator.apache.org/sling/site/provisioning-and-startup.html
I would like to ideally do something in between like so:
Get a binary copy of the sling jar
Create a folder with sub-folders like /1 /10 /15
Put my bundles in the various subfolders
Configure sling.properties to point to the folder
Start sling and have all bundles in the sub-folders installed and started
- Aaron Zeckoski
===
Currently, as you say in (1), the BootstrapInstaller of the Sling
launchpad looks into its own resources enclosed in the JAR or WAR file
for bundles to install on startup.
How about extending this mechanism like this:
- Copy all bundles from enclosed resources to
${sling.home}/startup. This gives something like
${sling.home}/startup/0, /1, /10, /15, ...
Existing files are only replaced if the files
enclosed in the Sling launchpad jar/war file are
newer.
- Scan ${sling.home}/startup for bundles to install
in the same way as today the enclosed resources
are scanned directly.
So you could place your bundles in that structure and get them installed
at the requested start level (0 being default bundle start level).
A nice side effect of this is, that you can quickly see, which bundles
have been installed at all.
- Felix
=
I like this, and agree that this should replace the current mechanism.
How about adding a sling.properties option to completely ignore the
bundles that come from the Sling jar/war file? Might make it easier to
have precise control on what's installed.
-Bertrand
=
Maybe worth it to make this optional or controllable via a property in the
sling properties.
- Aaron Zeckoski
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-949) Upgrade to Felix Framework release 1.6.1
[ 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 Key: SLING-949 URL: https://issues.apache.org/jira/browse/SLING-949 Project: Sling Issue Type: Improvement Components: Launchpad Affects Versions: Launchpad Base 2.0.2 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Launchpad Base 2.0.4 The Apache Felix project is voting on the release of the framework release 1.6.1. If the vote is successfull in time for our release, we should upgrade. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Hudson build is still unstable: sling-contrib-1 .5 » Apache Sling Launchpad Contrib Testing #10
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/10/
Re: JCR2 upgrade plans ?
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 2.0 is officially out before upgrading to JCR 2.0. At current rate of things I would expect Jackrabbit 2.0 to be out sometime within the second half of this year. BR, Jukka Zitting
