Am Samstag, 19. September 2015, 17:22:03 CEST schrieb Vishesh Handa: > > It is important to note that we're talking about infrastructural > > consistency here, not code consistency. There is a distinction. <snip> > > My point over here was to illustrate that there are many parts to > building a project, the code, development, handling contributions, > handling bugs, infrastructure, etc. None of these *have* to be > consistent. The manifesto does not actually dictate terms of > "infrastructure". > > Relevant part - "Online services associated with the project are > either hosted on KDE infrastructure or have an action plan that > ensures continuity which is approved by the KDE system administration > team"
There is no guaranteed continuity with anything that is *written* to the github.com presence. Unless the KDE system admin team provides one by backup up the github.com presence and be prepared to host it in case of service outage or termination. -- Martin _______________________________________________ kde-community mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-community
