From: Jakub Narebski <jnareb@gmail.com>
To: D Sundstrom <sunds@peapod.net>
Cc: git@vger.kernel.org
Subject: Re: Simple commit mechanism for non-technical users
Date: Wed, 19 Aug 2009 01:10:03 -0700 (PDT) [thread overview]
Message-ID: <m37hx0ns13.fsf@localhost.localdomain> (raw)
In-Reply-To: <ef72456d0908180905u18593b63tdc850b8552db30b9@mail.gmail.com>
D Sundstrom <sunds@peapod.net> writes:
> I use git to manage all project artifacts, including documentation,
> proposals, presentations, and so on.
>
> However, I have a hard time convincing non-technical staff to learn
> enough about git or to take the time to go through the effort of
> committing changes to a repository. So the steady stream of email
> attachments with "Acme Specification v3" or "final final spemco
> proprosal" continues.
>
> I'd hoped there was a simple web interface that would allow a user to
> upload and commit a file to a repository, but I've had no luck finding
> one. (I've used cgit for browsing, but it is read-only).
Some of git web interfaces or git hosting software offer editing via
web interface. Neither gitweb nor cgit offers this; it is available
AFAIK in GitHub (but it is not open source, and server version GitHub:FI
isn't cheap).
You can use some wiki (there are some wikis with git backend,
e.g. ikiwiki, see http://git.or.cz/gitwiki/InterfacesFrontendsAndTools)
or CMS like Drupal instead. Note that wikis usually work in
lock-edit-unlock mode (no merging changes), and have per page (per file)
versioning.
Alternate solution would be to use one of GUIs for Git, like
e.g. git-gui or QGit, or filemanager integration / shell extension
like (for MS Windows) TortoiseGit or Git Extensions.
> Is anyone aware of a simple way I can have my non-technical users
> manage their documents against a git repository? Ideally this would
> involve no installation of software on their machine (unless it were
> compelling, for example, the Finder plugin for SVN on the mac was a
> great tool for these users; or at least those on a mac...)
What operating system? What do you use currently?
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-08-19 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 16:05 Simple commit mechanism for non-technical users D Sundstrom
2009-08-19 6:09 ` Chris Packham
2009-08-19 7:49 ` Johannes Schindelin
2009-08-19 8:25 ` Matthieu Moy
2009-08-19 10:20 ` Jeff King
2009-08-19 14:40 ` D Sundstrom
2009-08-19 8:10 ` Jakub Narebski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m37hx0ns13.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunds@peapod.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.