On 9 January 2014 22:56, Armin Le Grand <armin.le.gr...@me.com> wrote:

> On 09.01.2014 00:36, Jürgen Schmidt wrote:
>
>> On 1/8/14 7:57 PM, jan i wrote:
>>
> -----------------------------8<-----------------------------
>
>> please be aware that cwiki is not nearly as visited as mwiki, so putting
>>> it
>>> in cwiki is a real good hiding place.
>>>
>> exactly, we should use mediawiki whenever possible, we could move the
>> content from confluence to mediawiki to make it even more clear.
>> Important pages will be monitored and wrong or damaging changes can be
>> corrected.
>>
>
> I have updated that page (https://wiki.openoffice.org/wiki/Source_Code)
> now and added my current branches. How can I now add a link to a page where
> I want to document the state and development of my branch alg_writerframes?
> I do not want to do that in the list there, that will be too much.
>
thanks, I agree we should hold this list relative short. How about putting
a link at the end of your line (documentation) .


>
>>
>>>  In that form it may also give a preview of what may be coming to the
>>>> next
>>>> versions (without forcing it, it should be train model based). E.g. with
>>>> accessibility when it would have been documented there it would be more
>>>> clear where it comes from, evtl. how far it is progressed and if it
>>>> will be
>>>> in one of the next versions (e.g. include a single 'progress' percent
>>>> number).
>>>>
>>>>  I dont object to the idea, but do we really want  to that much red tape
>>> around using branches. I would for sure remove capstone/l10n40 and keep
>>> it
>>> local instead if I have to document in cwiki.
>>>
>>> please remember the more documentation (in, at least to me, and unkown
>>> wiki
>>> language) makes it more likely that people considering a branch stop the
>>> idea.
>>>
>> it should be no must to document in detail but a short paragraph
>> describing for what kind of work the branch in intended can help. And
>> more documentation can help developers to organize their work or can
>> help for collaboration to work with more people on the same branch.  But
>> again it should be no must if people lose interest because of the
>> documentation burden.
>>
>
> I think a short paragraph in the list on the page
> https://wiki.openoffice.org/wiki/Source_Code will be fine and not too
> much requirement to do for everyone. Maybe this could even be automated
> when someone creates a link (just adding the link to it, the creation date
> and the creator? Herbert, is that possible..?).
>
+1. The creator would be nice, We can change the layout to a table, that
would make it easy to fill out.


>
> I need the possibility to add an extra link there (probably assocciated to
> some "more..." text or similar) which leads to an extra page with extended
> documentation (I want to share info with another developer in a central
> place - this is the Wiki from my POV). This should of course not be
> mandatory, but possibe.
>
extra row in a table.

rgds
jan I.

>
> Sincerely,
>     Armin
>
>
>> Juergen
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Reply via email to