Re: [gentoo-dev] [experiment] Sunrise try 2

[Edward Catmur]

On Sat, 2006-06-24 at 13:05 +0200, Luca Barbato wrote:
> (from critics)
> - What is wrong with the model (each point 2 lines at least, 4 at most)
> - What you'd do as alternative as the criticized point ( 2 lines again)

* Simplicity: The FAQ claims that Sunrise is simpler than Bugzilla. It
is - for users. Contributing is a lot more involved than with Bugzilla;
Sunrise is supposed to be about making contributing easier.
- Admit this in the FAQ. Where possible, write svn wrappers to make the
contributing process easier.

* Security (from malicious contributors): Glad to see layman will only
track the reviewed/ tree; still, anyone who checks out the sunrise/ tree
(and has it in PORTDIR_OVERLAY) is vulnerable.
- Remove from the examples any suggestion that one should check out the
whole tree when contributing. Point out that one should not svn up
sunrise/ as part of updating Portage.

* Conflicts between contributors (technical): Alice adds an ebuild; Bob
makes a change; Alice makes another change and discovers it conflicts
with Bob's change in the repo. Alice has not used subversion and doesn't
know how to resolve conflicts.
- Document the subversion conflict resolution process. Advertise that
you will be available on IRC to help with these types of problems.
Explain to use "svn st -u" and "svn up" to sync before making changes.

* Conflicts between contributors (social): Alice adds an ebuild; Bob
makes a (maybe "obvious") change; Alice thinks the change is incorrect,
and, feeling that the ebuild is her property, reverts the change. A
revert war erupts. Many casualties.
- Create a social structure to enable Alice and Bob to communicate and
resolve their differences of opinion. Forums? Wiki? IRC? Bugzilla? I
would argue there should be One True location for this to occur; /not/
bugzilla (bugspam); /not/ IRC (impermanence).

* More to keep track of: With bugzilla you have a single URL, from which
you receive threaded email updates. Sunrise adds /two/ svn directories
plus whatever is used for discussion.
- Create a summary page that links to bugzilla and discussions, and
tracks versions and changes, and all other relevant information. Allow
(require?) contributors to subscribe to email updates from the summary
page.

That's all for now. I might think of more.

Ed

-- 
gentoo-dev@g.o mailing list