[PD-dev] overview of upstream sources?

[Roman Haefeli]

On Wed, 2015-12-16 at 14:34 +0100, katja wrote:
> With the decentralization of Pd lib version control it is hard to
> locate / identify upstream source repositories. Would it be feasible
> and useful to generate (and regularly update) an overview of forks
> based on http://git.puredata.info/cgit/, to be referenced from
> http://puredata.info/docs/developer/GettingPdSource?


I believe it would be hard to maintain such an overview. Who has to
maintain such a list? How can you control that people adhere to the
standards?

I would rather propose adding some mandatory meta information to deken
uploads. A package that can be downloaded from puredata.info should at
least contain the information which sources it was built from.

Further, I think it is the duty of the maintainer of a fork to make
clear what the origin of the fork is.

If those two things are considered, we have transparency and identifying
upstream should be feasible.

Roman

 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20151217/c2b0eabf/attachment.sig>