On 20 September 2015 at 23:55, David Narvaez <[email protected]> wrote: > On Sun, Sep 20, 2015 at 4:11 PM, Jaroslaw Staniek <[email protected]> wrote: >> Hi >> I'd like to ask if this can be technically feasible and something we want: > > <snip> > > The subject sounds to me like a terrible idea, but reading the IRC log > I don't think I understand exactly what you are asking for. In > particular, I don't understand how is this different from a web > interface for users to submit a fly-by patch and developers to apply > those patches, which I think is something phabricator would support.
This is about r-w git repo for KDE and non-KDE devs. In git times the need is easier to understand for someone who interacts with 3rd party projects at code level. What is your workflow in this case? Do you send git archives git via email or patch sets? And constantly merge? I hope you don't use a private git server because it's worse that any 'free as beer' git hosting solution because of the bus factor and complexity. > If you do mean a "Fork Me" button like in github then it must be > opt-in for project maintainers because I certainly don't want that > workflow in my project. The button is mentioned to note that it's possible to implement it the day when we have the open read-write repos feature (in contrast to currently 'hidden' behind KDE developer account system). PS: Freedom of forking - derivative works is not so terrible, it's a pilliar of FOSS. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek _______________________________________________ kde-community mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-community
