wishlist: public whiteboard on branch pages

[David Allouche]

Martin Pool wrote:
> On 16 Oct 2006, David Allouche <ddaa at canonical.com> wrote:
>> All approaches call for the implementation of a "discussion
>> subscription" functionality, allowing users to receive email
>> notifications when something is changed or added in the discussion.
> 
> Well, all these approaches could benefit from allowing people to
> subscribe, but they don't *require* subscriptions to be useful.  We can
> add that later.

Sure.

I have just been looking at whether any approach was needing this
feature more or less than the other. And I could not find any difference
there.

>> On the importance of tracking authors: the SABDFL previously opposed to
>> allowing product owners from editing branches associated to their
>> product because in some cases there can be strong tensions between a
>> product owner and some of the contributors. In the centralized version
>> control world, that translates into people just going away or in a fork.
>> In the decentralized version-control world, what can (and does) happen
>> is a gradual shift of the developer community away from the difficult
>> maintainer.
> 
> I think if relations have got so bad that they need enforced permissions
> to prevent people changing each others branches, then the product will
> probably just fork.

I absolutely agree, I was merely channeling Mark here.

> 
>> My preferred solution is the micro-wiki, just because it's the simplest
>> possible way of doing it. Additional features (history tracking, bans,
>> access control, etc.) can be easily added later and it's probably widely
>> reusable in many places on Launchpad. But before doing it we need the
>> SABDFL to revise the policy against allowing people other than the
>> registrant from editing branch details.
>>
>> My least-preferred solution is the bulletin-board, because of its
>> append-only nature.
> 
> I think adding a micro-wiki would be great.  (It works very well in
> Trac.)  As you say, it's reusable in many other places.  To start with,
> simply storing text and rendering it as text would be enough.

I completely agree.

Let's just give edit permission on the branch title, summary, lifecycle
and whiteboard to the owner of the product of the branch.

Generally, it would be good to have a wiki-like historical record of
changes on most objects (product, productseries, branch, etc.) similar
to what we have now on bugs.

-- 
                                                            -- ddaa

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/launchpad-users/attachments/20061025/f5a6bf5b/attachment.pgp