You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bloodhound.apache.org by Olemis Lang <ol...@gmail.com> on 2012/11/10 00:34:39 UTC

Bloodhound Enhancement Proposals wiki docs hierarchy WAS: Multi product enhancements

On 11/7/12, Olemis Lang <ol...@gmail.com> wrote:
> On 11/7/12, Jure Zitnik <ju...@digiverse.si> wrote:
[...]
>
> Nonetheless in advance
> I suggest to summarize this discussion in the form of a wiki page we
> all can edit , and discuss each change @ bh-dev . Fact is that often
> it's hard to know what's the actual shape of some feature by reading
> discussions taking place at the ML ... that's what the wiki page is
> for .
>

Ok . I'll be writing an inital draft of a proposal for multi products
architecture that will be the foundation to get that done , once many
of us will express our opinions and enhance it in such a manner that a
bunch of relevant issues might be identified in advance . That will
allow us to see the big picture (the most of it ;) , summarize the
latest state and evolution of proposed enhanced , and ensure we work
on the right direction .

This is what I plan to create (BEP = Bloodhound Enhancement Proposal
... not Black Eyed Peas ... :P ) .

  1. Wiki and ReST templates for writing BEPs .
      Initially I'm thinking of a modified version of
      PEP 9 [1]_ and PEP 12 [2]_
  2. Wiki page for BEP introduction / overview
      somehow like PEP 1 [3]_ , PEP 9 [1]_ and PEP 12 [2]_ and
  3. Numerical Index , like in PEP 0 [4]_
  4. Index by category , like in PEP 0 [4]_

I'll remove and update many parts of these PEPs to adequate resulting
text to our current conditions (e.g. we won't have a community member
acting as BEP editor , etc , etc ...) .

Any comments ?

.. [1] Sample Plaintext PEP Template
       (http://www.python.org/dev/peps/pep-0009/)

.. [2] Sample reStructuredText PEP Template
       (http://www.python.org/dev/peps/pep-0012/)

.. [3] PEP Purpose and Guidelines
       (http://www.python.org/dev/peps/pep-0001/)

.. [4] Index of Python Enhancement Proposals (PEPs)
       (http://www.python.org/dev/peps/)

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

Re: Bloodhound Enhancement Proposals wiki docs hierarchy WAS: Multi product enhancements

Posted by Olemis Lang <ol...@gmail.com>.

On 11/12/12, Olemis Lang <ol...@gmail.com> wrote:
> ... and the first BEP goes for ... ticket workflow !!!
> :)
>
> It'd be nice to install WikinfoPlugin [2]_ (or alike) @ ASF issue
> tracker in order to automatically fill with meaningful values the TODO
> fields highlighted in BEP #1 header preamble .
>

I forgot something . Shall we describe ticket actions too ?

> BEP #2 will document Bloodhound widgets API (priority = low)
> BEP #3 will document Multi-product arcitecture (priority = high)
>
> .. [1] BEP 1 : Bloodhound ticket workflow
>         (https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0001)
>
> .. [2] WikinfoPlugin @ t-h.o
>         (http://trac-hacks.org/wiki/WikinfoPlugin)
>

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

Re: Bloodhound Enhancement Proposals wiki docs hierarchy WAS: Multi product enhancements

Posted by Olemis Lang <ol...@gmail.com>.

... and the first BEP goes for ... ticket workflow !!!
:)

It'd be nice to install WikinfoPlugin [2]_ (or alike) @ ASF issue
tracker in order to automatically fill with meaningful values the TODO
fields highlighted in BEP #1 header preamble .

BEP #2 will document Bloodhound widgets API (priority = low)
BEP #3 will document Multi-product arcitecture (priority = high)

.. [1] BEP 1 : Bloodhound ticket workflow
        (https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0001)

.. [2] WikinfoPlugin @ t-h.o
        (http://trac-hacks.org/wiki/WikinfoPlugin)




-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

Re: Bloodhound Enhancement Proposals wiki docs hierarchy WAS: Multi product enhancements

Posted by Olemis Lang <ol...@gmail.com>.

I have added some wiki pages containing modified versions of
Python-dev process PEPs related to enhancement proposals themselves .
I have not finished the modifications needed in these pages ,

Proposals/Formats/RestructuredText
Proposals/Formats/WikiFormatting

... and thereby you'll only see a text akin to the original PEP text .
Work on this direction is scheduled for next weekend .

Now that we have this I'll start writing the so-mentioned initial
proposal for mutli-product enhancements considering that format. IMO
we should have another similar document describing the workflow i.e.
summarizing the work done in #194 .


On 11/9/12, Olemis Lang <ol...@gmail.com> wrote:
> On 11/7/12, Olemis Lang <ol...@gmail.com> wrote:
>> On 11/7/12, Jure Zitnik <ju...@digiverse.si> wrote:
> [...]
>>
>> Nonetheless in advance
>> I suggest to summarize this discussion in the form of a wiki page we
>> all can edit , and discuss each change @ bh-dev . Fact is that often
>> it's hard to know what's the actual shape of some feature by reading
>> discussions taking place at the ML ... that's what the wiki page is
>> for .
>>
>
> Ok . I'll be writing an inital draft of a proposal for multi products
> architecture that will be the foundation to get that done , once many
> of us will express our opinions and enhance it in such a manner that a
> bunch of relevant issues might be identified in advance . That will
> allow us to see the big picture (the most of it ;) , summarize the
> latest state and evolution of proposed enhanced , and ensure we work
> on the right direction .
>
> This is what I plan to create (BEP = Bloodhound Enhancement Proposal
> ... not Black Eyed Peas ... :P ) .
>
>   1. Wiki and ReST templates for writing BEPs .
>       Initially I'm thinking of a modified version of
>       PEP 9 [1]_ and PEP 12 [2]_
>   2. Wiki page for BEP introduction / overview
>       somehow like PEP 1 [3]_ , PEP 9 [1]_ and PEP 12 [2]_ and
>   3. Numerical Index , like in PEP 0 [4]_
>   4. Index by category , like in PEP 0 [4]_
>
> I'll remove and update many parts of these PEPs to adequate resulting
> text to our current conditions (e.g. we won't have a community member
> acting as BEP editor , etc , etc ...) .
>
> Any comments ?
>
> .. [1] Sample Plaintext PEP Template
>        (http://www.python.org/dev/peps/pep-0009/)
>
> .. [2] Sample reStructuredText PEP Template
>        (http://www.python.org/dev/peps/pep-0012/)
>
> .. [3] PEP Purpose and Guidelines
>        (http://www.python.org/dev/peps/pep-0001/)
>
> .. [4] Index of Python Enhancement Proposals (PEPs)
>        (http://www.python.org/dev/peps/)
>
> --
> Regards,
>
> Olemis.
>
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
>
> Featured article:
>


-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article: