Re: KDE-Promo Repository

On Friday 20 July 2012 15:18:49 Seth wrote:
> > On Wednesday 16 May 2012 03:07:29 Valorie Zimmerman wrote:
> > > Bumping again...... A bit of googling took me to
> > > http://stackoverflow.com/questions/29292/version-control-for-graphics
> > > which has some ideas. More where that came from if you google
> > > 
> > > version control system art
> > > 
> > > Has anybody reached out to Gnome or any of the other desktop or distro
> > > teams for their ideas?
> > 
> > I believe Fedora has a reasonable workflow for art but I haven't had
> > time
> > to have a good look at it. Bruno, on CC, does openSUSE art. Eugene, too,
> > btw. Maybe they are interested - this might be something to discuss at a
> > conf, yes...
> > 
> > > Valorie
> > > 
> > > On Sat, Apr 14, 2012 at 3:40 AM, Jos Poortvliet <[email protected]> 
wrote:
> > > > On Friday 16 March 2012 12:46:22 Anne-Marie Mahfouf wrote:
> > > >> On 03/14/2012 01:12 PM, Stuart Jarvis wrote:
> > > >> > On Tuesday 13 March 2012 18:09:13 Claudia Rauch wrote:
> > > >> >> On 13 March 2012 18:01, James Cain<[email protected]>  
wrote:
> > > >> >>> I'm bumping this just for the sake of it staying alive. I would
> > > >> >>> like to
> > > >> >>> see
> > > >> >>> at least see something done. Ideally, maybe a full-blown Promo
> > > >> >>> website.
> > > >> >>> Canonical has several resources around, including
> > > >> >>> this:https://wiki.ubuntu.com/MarketingTeam/Projects
> > > >> >>> 
> > > >> >>> I like because it's a one-stop shop for all things Promo.
> > > >> >> 
> > > >> >> There ishttp://community.kde.org/Promo  which is arguably a bit
> > > >> >> hidden, and it needs some people to regularly update the pages
> > > >> >> and
> > > >> >> sources. It is a start, nonetheless.
> > > >> > 
> > > >> > Yes, we could do a lot more with this than we do at the moment.
> > > >> > 
> > > >> >> Ideas on how to make this more useful are always good :)
> > > >> > 
> > > >> > The ideas floating around about using SVN/git are interesting. I
> > > >> > wouldn't
> > > >> > want to force a new contributor to have to learn those first, but
> > > >> > accessing stuff from either via a web interface is easy and those
> > > >> > who are
> > > >> > comfortable with it could handle uploading stuff.
> > > >> > 
> > > >> > If we go down that route, I'd still like the wiki to be some kind
> > > >> > of
> > > >> > front-
> > > >> > end, with links to the relevant resources (or at least areas) in
> > > >> > the
> > > >> > cvs.
> > > >> > 
> > > >> >>> On Tue, Mar 6, 2012 at 12:15 PM, Anne-Marie Mahfouf
> > > >> >>> 
> > > >> >>> <[email protected]>  wrote:
> > > >> >>>> Will there be a Promo sprint this year?
> > > >> > 
> > > >> > It would be good to have a small focussed sprint to concentrate
> > > >> > on
> > > >> > this
> > > >> > one
> > > >> > issue (sprints, including the last promo sprint, can suffer from
> > > >> > trying to do too many things at once).
> > > >> > 
> > > >> > I wouldn't have time to organise such a thing until this Autumn
> > > >> > at
> > > >> > least
> > > >> > and to be honest I'd rather someone else took care of it since I
> > > >> > did
> > > >> > it
> > > >> > last time - and it should be in a different venue, I think. We
> > > >> > could
> > > >> > also
> > > >> > consider a virtual sprint where we all get together some weekend
> > > >> > and
> > > >> > work
> > > >> > on this, but it can be harder to put the time aside when you're
> > > >> > not
> > > >> > physically away somewhere.
> > > >> > 
> > > >> > So perhaps we can ask:
> > > >> > - Who would be potentially interested in working at such a
> > > >> > focussed
> > > >> > sprint - Where do you live (to give some idea of venues)
> > > >> > - Who could organise such a thing? You need:
> > > >> > -- to find a (free) venue
> > > >> > -- find cheap accommodation
> > > >> > -- harass people to tell you whether they will attend and their
> > > >> > costs -- propose it to the board
> > > >> > -- (ideally) give the attendees some guidance on how to get to
> > > >> > the
> > > >> > location
> > > >> > 
> > > >> > Cheers,
> > > >> > Stu
> > > >> 
> > > >> I don't have time to organize anything unfortunately. There will be
> > > >> a
> > > >> KDE meeting in Randa (Switzerland) in September and this location
> > > >> can
> > > >> accommodate several groups. Maybe that would be an option. It needs
> > > >> someone in contact with Mario Fux and KDE eV to set it up but
> > > >> accommodation and food would be provided.
> > > >> 
> > > >> The wiki does not fulfill any real life needs: there are no new
> > > >> slides
> > > >> and templates to use in talks on http://www.kde.org/kdeslides/, the
> > > >> artwork in not usable as it's too focused and lacks sources. The
> > > >> open
> > > >> content is old and not so open (I see .doc files...) The link to
> > > >> Wade
> > > >> Picasa posters leads to Wade personal pictures.
> > > >> git and svn are not difficult to use as they have a web interface.
> > > >> We
> > > >> will never have any interesting and up-to-date material if we do
> > > >> not
> > > >> have a repository. I also mentioned in another mail that the French
> > > >> people wanted to translate the KDE booklet and start some scripts
> > > >> for
> > > >> demo machines. They had an interest in promoting KDE but this
> > > >> interest
> > > >> was cut flat because there is nothing to start from.
> > > >> 
> > > >> The wiki should explain where to find things but those things can
> > > >> only
> > > >> exist from sources in a repository. If we have no sources we can't
> > > >> do
> > > >> promo world wide.
> > > > 
> > > > Stu mentioned two issues:
> > > > 1 finding the stuff
> > > > 2 uploading the stuff
> > > > 
> > > > The wiki is doable for 1 (needs maintenance) but sucks for 2. Git is
> > > > Ok-ish for 2 (not easy to use for artists/newbies, however!) but
> > > > sucks
> > > > for 1.
> > > > 
> > > > In openSUSE we have this exact same problem. What would be needed is
> > > > a
> > > > web interface to Git (or another scm) which has easy options to look
> > > > for artwork, see current and old versions and upload newer versions.
> > > > We
> > > > currently use github as it offers some of these options but it is
> > > > far
> > > > from perfect.
> > > > 
> > > > Some openSUSE people are interested in helping to solve this issue
> > > > but
> > > > nobody ever really sat down, wrote down requirements and worked on a
> > > > solution.
> > > > 
> > > > IF wee get to that point where we have people able and willing to
> > > > work
> > > > on this during a sprint, I would suggest to reach out to others. At
> > > > least, openSUSE would be interested in joining, helping with code
> > > > and
> > > > sponsoring. Kubuntu might need this, but so does (I'd recon) GNOME.
> > > > Heck, artwork/promo materials are an issue for ALL free software
> > > > projects except those with significant financial resources...
> > > > 
> > > > An effort to build any solution which might be deployed for multiple
> > > > projects would get all support I can muster up.
> > > > 
> > > >> Best regards,
> > > >> 
> > > >> Anne-Marie
> 
> Fedora art team uses sparkleshare, which is a git-based frontend for
> sharing files.
> 
> It doesn't work exactly like checking in and out code, but it's pretty
> similar; the difference is you just have to save a rendered version of
> what you end up with so people can see the diff between an old and a new
> version. It's not exactly like rolling back a commit in traditional git,
> at least not the way programmers probably think of it.

Ah, so they don't have a good solution either. In openSUSE we use git (via 
github) as well but it just isn't suited for this. I personally use Dolphin 
for the committing part, almost as easy as sparkleshare and much more 
powerful but at some point it'd be nice to have a 'proper' solution...

> - seth


_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEABECAAYFAlANJAwACgkQ+wgQ1AD35iyczACgtHszHhFJFAHT+sK27JhrL5+8
G3gAoK+iA7OIizUc5mcke4h3I3NFzWuY
=RdB1
-----END PGP SIGNATURE-----