You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by David Blevins <da...@gmail.com> on 2012/06/04 04:29:17 UTC

Website permissions

Charles had poked me a while back on writing docs for the OSGi support.

Currently, writing docs is a matter of sending a patch:

  http://svn.apache.org/repos/asf/openejb/site/trunk/content

It occurs to me as well that, we have complete control of our svn permissions and we could just open up a section of the site for any ASF committer to update.

Maybe, http://svn.apache.org/repos/asf/openejb/site/trunk/content/contrib/

Thoughts?


-David


Re: Website permissions

Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
OK, +1

JLouis

2012/6/4 Romain Manni-Bucau <rm...@gmail.com>

> +1
> Le 4 juin 2012 07:43, "David Blevins" <da...@gmail.com> a écrit :
>
> >
> > On Jun 3, 2012, at 9:53 PM, Romain Manni-Bucau wrote:
> >
> > > I'd say +1 for contribs (= extensions to what we provide) but here
> that's
> > > more /osgi no?
> >
> > It's really about making it a little easier to write a doc than about
> > creating the best organization for information on the website.
> >
> > Someone could put something in contrib and then we can move it to
> wherever
> > it needs to go.
> >
> >
> > -David
> >
> >
>

Re: Website permissions

Posted by Romain Manni-Bucau <rm...@gmail.com>.
+1
Le 4 juin 2012 07:43, "David Blevins" <da...@gmail.com> a écrit :

>
> On Jun 3, 2012, at 9:53 PM, Romain Manni-Bucau wrote:
>
> > I'd say +1 for contribs (= extensions to what we provide) but here that's
> > more /osgi no?
>
> It's really about making it a little easier to write a doc than about
> creating the best organization for information on the website.
>
> Someone could put something in contrib and then we can move it to wherever
> it needs to go.
>
>
> -David
>
>

Re: Website permissions

Posted by David Blevins <da...@gmail.com>.
On Jun 3, 2012, at 9:53 PM, Romain Manni-Bucau wrote:

> I'd say +1 for contribs (= extensions to what we provide) but here that's
> more /osgi no?

It's really about making it a little easier to write a doc than about creating the best organization for information on the website.

Someone could put something in contrib and then we can move it to wherever it needs to go.


-David


Re: Website permissions

Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hmm,

I'd say +1 for contribs (= extensions to what we provide) but here that's
more /osgi no?

- Romain
Le 4 juin 2012 04:29, "David Blevins" <da...@gmail.com> a écrit :

> Charles had poked me a while back on writing docs for the OSGi support.
>
> Currently, writing docs is a matter of sending a patch:
>
>  http://svn.apache.org/repos/asf/openejb/site/trunk/content
>
> It occurs to me as well that, we have complete control of our svn
> permissions and we could just open up a section of the site for any ASF
> committer to update.
>
> Maybe, http://svn.apache.org/repos/asf/openejb/site/trunk/content/contrib/
>
> Thoughts?
>
>
> -David
>
>

Re: Website permissions

Posted by David Blevins <da...@gmail.com>.
Seems like there was lazy consensus to have some kind of area like that.  I'll try and set it up later today.

-David

On Jun 13, 2012, at 12:28 AM, Charles Moulliard wrote:

> Hi David,
> 
> Have you received thoughts after posting this email ?
> 
> Regards,
> 
> Charles
> 
> On Mon, Jun 4, 2012 at 4:29 AM, David Blevins <da...@gmail.com> wrote:
> Charles had poked me a while back on writing docs for the OSGi support.
> 
> Currently, writing docs is a matter of sending a patch:
> 
>  http://svn.apache.org/repos/asf/openejb/site/trunk/content
> 
> It occurs to me as well that, we have complete control of our svn permissions and we could just open up a section of the site for any ASF committer to update.
> 
> Maybe, http://svn.apache.org/repos/asf/openejb/site/trunk/content/contrib/
> 
> Thoughts?
> 
> 
> -David
> 
> 


Re: Website permissions

Posted by David Blevins <da...@gmail.com>.
On Jun 27, 2012, at 12:03 AM, Charles Moulliard wrote:

> I have tried to submit a new section page but get this error next :
> 
> Error
> 
> The operation is forbidden by the server: Commit failed (details follow):: Changing file '/usr/local/cms/wc/openejb/cmoulliard-j5hoLl/trunk/content/documentation.mdtext' is forbidden by the server: Access to '/repos/asf/!svn/txr/1354344-tkki/openejb/site/trunk/content/documentation.mdtext' forbidden at /usr/local/cms/webgui/lib/ASF/CMS/WC/Commit.pm line 64

Try this flow 'Edit => Diff => Mail Diff'


-David


Re: Website permissions

Posted by Charles Moulliard <cm...@gmail.com>.
I have tried to submit a new section page but get this error next :

Error

The operation is forbidden by the server: Commit failed (details
follow):: Changing file
'/usr/local/cms/wc/openejb/cmoulliard-j5hoLl/trunk/content/documentation.mdtext'
is forbidden by the server: Access to
'/repos/asf/!svn/txr/1354344-tkki/openejb/site/trunk/content/documentation.mdtext'
forbidden at /usr/local/cms/webgui/lib/ASF/CMS/WC/Commit.pm line 64


On Wed, Jun 27, 2012 at 8:59 AM, Charles Moulliard <cm...@gmail.com>wrote:

> I have followed the instructions (video) to edit, staged and move
> modifications in production using Apache CMS / Bookmarlet but on the web
> site and also in the video I don't see any button to create a new page. Is
> it because I don't have the rights on openejb.apache.org - cms ?
>
> On Tue, Jun 26, 2012 at 7:54 PM, David Blevins <da...@gmail.com>wrote:
>
>>
>> On Jun 25, 2012, at 10:53 PM, Charles Moulliard wrote:
>>
>> > Would you like that I use Apache CMS or that I publish some markdown
>> pages here (http://svn.apache.org/repos/asf/openejb/site/trunk/content/)
>> ?
>>
>> The Apache CMS is backed by that section of SVN, so it's more or less the
>> same.  You don't have direct access and it probably sounds more complicated
>> to explain, but in short think github; the CMS allows you to clone the site
>> and submit "pull requests".
>>
>> Basically you just click the little blue pencil icon, edit away, then
>> click 'Submit' and make sure 'Quick Mail' is selected.
>>
>> > Do you know if we can use pegdown (https://github.com/sirthias/pegdown)
>> as they support tables ?
>>
>> At the moment only markdown is supported.
>>
>> We could certainly switch all the docs over to something else if we
>> wanted to do that at the project level, but that would probably be a
>> different discussion and we'd need some time to make the CMS be able to
>> handle that format.
>>
>> > Can we use wiki of confluence ?
>>
>> Ideally we'd keep driving features into the CMS till people feel they
>> "have access" and don't feel compelled to use a wiki or confluence anymore.
>>
>> So let's definitely use the CMS and definitely feel encouraged to say X,
>> Y or Z is a PITA and should be fixed :)
>>
>>
>> -David
>>
>>
>> > On 26/06/12 03:56, David Blevins wrote:
>> >> Hi Charles,
>> >>
>> >> Can you give the new editing links a try?  Not sure we have all the
>> kinks worked out in terms of existing Apache committers editing docs.
>>  Would love to use you as a guinea pig to see if we can smooth that process
>> out.
>> >>
>> >> We should probably just give you commit eventually, but I'd love to
>> see if we can streamline the "ASF contributor" process as well.
>> >>
>> >> Any help in that is greatly appreciated!
>> >>
>> >>
>> >> -David
>> >>
>> >> On Jun 13, 2012, at 12:28 AM, Charles Moulliard wrote:
>> >>
>> >>> Hi David,
>> >>>
>> >>> Have you received thoughts after posting this email ?
>> >>>
>> >>> Regards,
>> >>>
>> >>> Charles
>> >>>
>> >>> On Mon, Jun 4, 2012 at 4:29 AM, David Blevins<da...@gmail.com>
>>  wrote:
>> >>> Charles had poked me a while back on writing docs for the OSGi
>> support.
>> >>>
>> >>> Currently, writing docs is a matter of sending a patch:
>> >>>
>> >>>  http://svn.apache.org/repos/asf/openejb/site/trunk/content
>> >>>
>> >>> It occurs to me as well that, we have complete control of our svn
>> permissions and we could just open up a section of the site for any ASF
>> committer to update.
>> >>>
>> >>> Maybe,
>> http://svn.apache.org/repos/asf/openejb/site/trunk/content/contrib/
>> >>>
>> >>> Thoughts?
>> >>>
>> >>>
>> >>> -David
>> >>>
>> >>>
>>
>>
>

Re: Website permissions

Posted by Charles Moulliard <cm...@gmail.com>.
I have followed the instructions (video) to edit, staged and move
modifications in production using Apache CMS / Bookmarlet but on the web
site and also in the video I don't see any button to create a new page. Is
it because I don't have the rights on openejb.apache.org - cms ?

On Tue, Jun 26, 2012 at 7:54 PM, David Blevins <da...@gmail.com>wrote:

>
> On Jun 25, 2012, at 10:53 PM, Charles Moulliard wrote:
>
> > Would you like that I use Apache CMS or that I publish some markdown
> pages here (http://svn.apache.org/repos/asf/openejb/site/trunk/content/) ?
>
> The Apache CMS is backed by that section of SVN, so it's more or less the
> same.  You don't have direct access and it probably sounds more complicated
> to explain, but in short think github; the CMS allows you to clone the site
> and submit "pull requests".
>
> Basically you just click the little blue pencil icon, edit away, then
> click 'Submit' and make sure 'Quick Mail' is selected.
>
> > Do you know if we can use pegdown (https://github.com/sirthias/pegdown)
> as they support tables ?
>
> At the moment only markdown is supported.
>
> We could certainly switch all the docs over to something else if we wanted
> to do that at the project level, but that would probably be a different
> discussion and we'd need some time to make the CMS be able to handle that
> format.
>
> > Can we use wiki of confluence ?
>
> Ideally we'd keep driving features into the CMS till people feel they
> "have access" and don't feel compelled to use a wiki or confluence anymore.
>
> So let's definitely use the CMS and definitely feel encouraged to say X, Y
> or Z is a PITA and should be fixed :)
>
>
> -David
>
>
> > On 26/06/12 03:56, David Blevins wrote:
> >> Hi Charles,
> >>
> >> Can you give the new editing links a try?  Not sure we have all the
> kinks worked out in terms of existing Apache committers editing docs.
>  Would love to use you as a guinea pig to see if we can smooth that process
> out.
> >>
> >> We should probably just give you commit eventually, but I'd love to see
> if we can streamline the "ASF contributor" process as well.
> >>
> >> Any help in that is greatly appreciated!
> >>
> >>
> >> -David
> >>
> >> On Jun 13, 2012, at 12:28 AM, Charles Moulliard wrote:
> >>
> >>> Hi David,
> >>>
> >>> Have you received thoughts after posting this email ?
> >>>
> >>> Regards,
> >>>
> >>> Charles
> >>>
> >>> On Mon, Jun 4, 2012 at 4:29 AM, David Blevins<da...@gmail.com>
>  wrote:
> >>> Charles had poked me a while back on writing docs for the OSGi support.
> >>>
> >>> Currently, writing docs is a matter of sending a patch:
> >>>
> >>>  http://svn.apache.org/repos/asf/openejb/site/trunk/content
> >>>
> >>> It occurs to me as well that, we have complete control of our svn
> permissions and we could just open up a section of the site for any ASF
> committer to update.
> >>>
> >>> Maybe,
> http://svn.apache.org/repos/asf/openejb/site/trunk/content/contrib/
> >>>
> >>> Thoughts?
> >>>
> >>>
> >>> -David
> >>>
> >>>
>
>

Re: Website permissions

Posted by David Blevins <da...@gmail.com>.
On Jun 25, 2012, at 10:53 PM, Charles Moulliard wrote:

> Would you like that I use Apache CMS or that I publish some markdown pages here (http://svn.apache.org/repos/asf/openejb/site/trunk/content/) ?

The Apache CMS is backed by that section of SVN, so it's more or less the same.  You don't have direct access and it probably sounds more complicated to explain, but in short think github; the CMS allows you to clone the site and submit "pull requests".

Basically you just click the little blue pencil icon, edit away, then click 'Submit' and make sure 'Quick Mail' is selected.

> Do you know if we can use pegdown (https://github.com/sirthias/pegdown) as they support tables ?

At the moment only markdown is supported.

We could certainly switch all the docs over to something else if we wanted to do that at the project level, but that would probably be a different discussion and we'd need some time to make the CMS be able to handle that format.

> Can we use wiki of confluence ?

Ideally we'd keep driving features into the CMS till people feel they "have access" and don't feel compelled to use a wiki or confluence anymore.

So let's definitely use the CMS and definitely feel encouraged to say X, Y or Z is a PITA and should be fixed :)


-David


> On 26/06/12 03:56, David Blevins wrote:
>> Hi Charles,
>> 
>> Can you give the new editing links a try?  Not sure we have all the kinks worked out in terms of existing Apache committers editing docs.  Would love to use you as a guinea pig to see if we can smooth that process out.
>> 
>> We should probably just give you commit eventually, but I'd love to see if we can streamline the "ASF contributor" process as well.
>> 
>> Any help in that is greatly appreciated!
>> 
>> 
>> -David
>> 
>> On Jun 13, 2012, at 12:28 AM, Charles Moulliard wrote:
>> 
>>> Hi David,
>>> 
>>> Have you received thoughts after posting this email ?
>>> 
>>> Regards,
>>> 
>>> Charles
>>> 
>>> On Mon, Jun 4, 2012 at 4:29 AM, David Blevins<da...@gmail.com>  wrote:
>>> Charles had poked me a while back on writing docs for the OSGi support.
>>> 
>>> Currently, writing docs is a matter of sending a patch:
>>> 
>>>  http://svn.apache.org/repos/asf/openejb/site/trunk/content
>>> 
>>> It occurs to me as well that, we have complete control of our svn permissions and we could just open up a section of the site for any ASF committer to update.
>>> 
>>> Maybe, http://svn.apache.org/repos/asf/openejb/site/trunk/content/contrib/
>>> 
>>> Thoughts?
>>> 
>>> 
>>> -David
>>> 
>>> 


Re: Website permissions

Posted by Charles Moulliard <cm...@gmail.com>.
Hi David,

Would you like that I use Apache CMS or that I publish some markdown 
pages here (http://svn.apache.org/repos/asf/openejb/site/trunk/content/) ?
Do you know if we can use pegdown (https://github.com/sirthias/pegdown) 
as they support tables ? Can we use wiki of confluence ?

Regards,

Charles

On 26/06/12 03:56, David Blevins wrote:
> Hi Charles,
>
> Can you give the new editing links a try?  Not sure we have all the kinks worked out in terms of existing Apache committers editing docs.  Would love to use you as a guinea pig to see if we can smooth that process out.
>
> We should probably just give you commit eventually, but I'd love to see if we can streamline the "ASF contributor" process as well.
>
> Any help in that is greatly appreciated!
>
>
> -David
>
> On Jun 13, 2012, at 12:28 AM, Charles Moulliard wrote:
>
>> Hi David,
>>
>> Have you received thoughts after posting this email ?
>>
>> Regards,
>>
>> Charles
>>
>> On Mon, Jun 4, 2012 at 4:29 AM, David Blevins<da...@gmail.com>  wrote:
>> Charles had poked me a while back on writing docs for the OSGi support.
>>
>> Currently, writing docs is a matter of sending a patch:
>>
>>   http://svn.apache.org/repos/asf/openejb/site/trunk/content
>>
>> It occurs to me as well that, we have complete control of our svn permissions and we could just open up a section of the site for any ASF committer to update.
>>
>> Maybe, http://svn.apache.org/repos/asf/openejb/site/trunk/content/contrib/
>>
>> Thoughts?
>>
>>
>> -David
>>
>>

Re: Website permissions

Posted by David Blevins <da...@gmail.com>.
Hi Charles,

Can you give the new editing links a try?  Not sure we have all the kinks worked out in terms of existing Apache committers editing docs.  Would love to use you as a guinea pig to see if we can smooth that process out.

We should probably just give you commit eventually, but I'd love to see if we can streamline the "ASF contributor" process as well.

Any help in that is greatly appreciated!


-David

On Jun 13, 2012, at 12:28 AM, Charles Moulliard wrote:

> Hi David,
> 
> Have you received thoughts after posting this email ?
> 
> Regards,
> 
> Charles
> 
> On Mon, Jun 4, 2012 at 4:29 AM, David Blevins <da...@gmail.com> wrote:
> Charles had poked me a while back on writing docs for the OSGi support.
> 
> Currently, writing docs is a matter of sending a patch:
> 
>  http://svn.apache.org/repos/asf/openejb/site/trunk/content
> 
> It occurs to me as well that, we have complete control of our svn permissions and we could just open up a section of the site for any ASF committer to update.
> 
> Maybe, http://svn.apache.org/repos/asf/openejb/site/trunk/content/contrib/
> 
> Thoughts?
> 
> 
> -David
> 
> 


Re: Website permissions

Posted by Charles Moulliard <cm...@gmail.com>.
Hi David,

Have you received thoughts after posting this email ?

Regards,

Charles

On Mon, Jun 4, 2012 at 4:29 AM, David Blevins <da...@gmail.com>wrote:

> Charles had poked me a while back on writing docs for the OSGi support.
>
> Currently, writing docs is a matter of sending a patch:
>
>  http://svn.apache.org/repos/asf/openejb/site/trunk/content
>
> It occurs to me as well that, we have complete control of our svn
> permissions and we could just open up a section of the site for any ASF
> committer to update.
>
> Maybe, http://svn.apache.org/repos/asf/openejb/site/trunk/content/contrib/
>
> Thoughts?
>
>
> -David
>
>