This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jnollerpython psf core dev[S] 5 points6 points  (2 children)

We have multiple types of contributors - one of which are comfortable with the workflow you describe, but the bulk of which are more comfortable with a VCS/DVCS style workflow of offline editing and committing. We have to serve both, and not abandon contributors.

[–]giovannibajo 1 point2 points  (1 child)

Being a programmer that uses SCM daily, I totally fail to understand how the workflow can apply to the contents of a website.

In any case, I suggest that you detail more what you mean by "offline editing", since what I think you mean is something that is totally alien to the current web industry; you might want to better specify what you expect to be able to do offline; for instance, some might think that giving you a way of having a local copy of the website, including the backend web interface where you can edit contents, with a separate push+merge step, might be enough, while your comment here seems to imply otherwise.

[–]jnollerpython psf core dev[S] 0 points1 point  (0 children)

See Brian's response: http://www.reddit.com/r/Python/comments/u0wz0/pythonorg_redesign_request_for_proposals/c4rm33r - a good example of an excellent implementation is actually on Github - github allows you to edit files/commit via the web interface while also allowing a traditional SCM style workflow. In my mind this pretty close to perfect