[wp-hackers] Wordpress theme version control: Google Summer of Code proposal

[Jacob Gillespie]

I agree, and also from a UX perspective I don't think that SCM-specific
ideas should carry over into theme file version control.  For example, a
non-technical user of WordPress is not likely to know what a commit is, what
revision numbers mean, or even what a revision is.  They will be more
interested in a solution that gives them an "undo" function for changes that
they might make to their theme files.

It is true that users who are editing their theme files are more advanced
than ones who know nothing about HTML/CSS, however even if the solution was
not specific to one SCM (git, SVN, etc), IMHO the version control system
should work like the existing post version control system and not require
users to have preknowledge about SCMs or even require them to learn about
them.

Just my thoughts, though.

Jacob

On Thu, Apr 7, 2011 at 6:57 PM, scribu <mail at scribu.net> wrote:

> Oups... my actual reply:
>
>
> I see you intend to use svn for versioning. The problem with that is most
> people don't have svn installed on their server, being on shared hosting,
> which severely limits it's appeal.
>
> Also, by tieing it to svn, you also discourage users that prefer other
> SCMs,
> like git or mercurial.
>
> --
> http://scribu.net
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>