[Sugar-devel] How to find the repository of an activity?

[James Cameron]

On Thu, Sep 25, 2014 at 02:35:47PM -0300, Gonzalo Odiard wrote:
> Maybe we should make the repository field mandatory,
> then new releases would have it.

For now, just having the active developers accept "repository" as the
value to use, is enough.  As we change activities we can add it.

For future release, when an activity bundle is built from source, the
repository value could be added to the info file if it does not have
one.  It can come from git remote origin.  And add a hash.

On Thu, Sep 25, 2014 at 01:46:39PM -0400, Martin Abente wrote:
> I think this is human-layer problem, making it a software-layer
> problem will probably fire back, and will simply make _us_ fill
> these fields later... :/

Yes.  On the other hand, you, Gonzalo, and I have an implied
responsibility to do this when we make activity changes as part of
contract work for deployments or OLPC.

> +1, we should keep contacting the developers and then think what to
> do with activities with missing maintainers...

Missing maintainers equals fork.  This thread in sugar-devel@ is a
good start.  Maintainers not reading sugar-devel@ is already big
enough problem that we can't solve.

-- 
James Cameron
http://quozl.linux.org.au/