Design/GlitterGallery: Difference between revisions

Latest revision as of 09:01, 2 April 2015

About this WikiPage

This page contains information on the GlitterGallery project's association with the Fedora Project, an ongoing effort by the Fedora design team to ease collaboration among FLOSS designers. For general information about the project itself, you can look at it's documentation on the GitHub wiki[1].

[1] - https://github.com/glittergallery/GlitterGallery/wiki

People Involved

Emily Dirsh (emily AT glittergallery DOT net)
Mo Duffy (duffy AT fedoraproject DOT org)
Rohit Paul Kuruvilla (rohitkuruvill AT yahoo DOT co DOT in)
Sarup Banskota (sarup AT glittergallery DOT net)

Brief History

One fine day, Máirín(Mo) wrote this blog post[2] about her idea of an open collaboration space for FLOSS designers world over. At a GNOME UX hackfest in London soon after, a bunch of designers got together to discuss what would later become Design Hub. Emily and Mo came up with an early hacky concept and presented it at the Libre Graphics Meeting[3] 2012 in Vienna[4].

Sarup joined in 2013, Design Hub grew to GlitterGallery and went from idea to prototype. Sarup presented GlitterGallery, at the 2014 edition of the Libre Graphics Meeting held in Leipzig[4]. The proposal is to make GlitterGallery available for FLOSS designers to use, in a way that it fits into their workflow without involving much git-fu. In 2014, Rohit joined GlitterGallery as a GSoC student. He worked on improving the project's Git-centric bits.

There have been several contributors to the project since: https://github.com/glittergallery/GlitterGallery/graphs/contributors.

[2] - https://mairin.wordpress.com/2010/02/13/random-idea-for-design-collaboration-tool/

[3] - http://en.wikipedia.org/wiki/Libre_Graphics_Meeting

[4] - http://libregraphicsmeeting.org/2012/

[5] - http://libregraphicsmeeting.org/2014/

Talks & Coverage

Over time, GlitterGallery has been discussed at various events where other Fedora folk have been present.

Contributor	Event	Location	Type of coverage	Relevant Links
Emily Dirsh, Máirín Duffy	Libre Graphics Meeting 2012	Vienna	Talk	Video
Sarup Banskota	FOSSASIA 2014	Phnom Penh	Talk	slides
Sarup Banskota	Libre Graphics Meeting 2014	Leipzig	Talk	Video, slides, commonsmachinery, shuttleworthfoundation, lwn

Fedora Design Team Installation

A link to a working deployment will be always available on the GlitterGallery README[6].

[6] - https://github.com/glittergallery/GlitterGallery/blob/master/README.markdown

Meetings

We try to have weekly meetings every Wednesday on #glittergallery at Freenode.

Communication

Like/hate anything in particular? Just ping one of us and we'll follow up!

Sarup: sarup AT glittergallery DOT net Blog
Rohit: rohitkuruvilla AT yahoo DOT co DOT in Blog
Emily: edirsh AT redhat DOT com

Further links

[1] - Wiki: https://github.com/glittergallery/GlitterGallery/wiki

[2] - Mo's blog - https://mairin.wordpress.com/2010/02/13/random-idea-for-design-collaboration-tool/

[3] - LGM Wikipedia - http://en.wikipedia.org/wiki/Libre_Graphics_Meeting

[4] - LGM 2012, Vienna - http://libregraphicsmeeting.org/2012/

[5] - LGM 2014, Leipzig - http://libregraphicsmeeting.org/2014/

[6] - README - https://github.com/glittergallery/GlitterGallery/blob/master/README.markdown

@@ Line 1: / Line 1: @@
-{{Admon/note |This page is under construction!}}.
+== About this WikiPage==
-{{Admon/note |This page contains information pertaining GlitterGallery's relationship with Fedora. For the GlitterGallery project wiki, please visit: https://github.com/sarupbanskota/GlitterGallery/wiki.}}.
-== About GlitterGallery ==
+This page contains information on the GlitterGallery project's association with the Fedora Project, an ongoing effort by the Fedora design team to ease collaboration among FLOSS designers. For general information about the project itself, you can look at it's documentation on the GitHub wiki[1].
-GlitterGallery is an ongoing project that aims to improve the state of designer-designer and designer-developer collaboration. FLOSS developers have always had an edge with respect to the tools they have to help them with collaboration activity. Designers have had great tools to create art and designwork and have been producing awesome, but when it comes to working as a team spread across the world, the current state of collaboration fails.
+[1] - https://github.com/glittergallery/GlitterGallery/wiki
-GlitterGallery hopes to be able to change that. We're first going to be biased to SVG work, and then we'll slowly progress to accommodate everyone.
+== People Involved ==
-== People ==
 * Emily Dirsh (emily AT glittergallery DOT net)
+* Mo Duffy (duffy AT fedoraproject DOT org)
+* Rohit Paul Kuruvilla (rohitkuruvill AT yahoo DOT co DOT in)
 * Sarup Banskota (sarup AT glittergallery DOT net)
-* Mo Duffy (duffy AT fedoraproject DOT org)
-== History ==
+== Brief History ==
-Mo's idea, UX hackfest, Emily's programming, LGM presentation, Sarup joined in..., another LGM, release at Flock
+One fine day, [https://twitter.com/mairin Máirín](Mo) wrote this blog post[2] about her idea of an open collaboration space for FLOSS designers world over. At a GNOME UX hackfest in London soon after, a bunch of designers got together to discuss what would later become ''Design Hub''. [http://twitter.com/Emichan Emily] and Mo came up with an early hacky concept and presented it at the Libre Graphics Meeting[3] 2012 in Vienna[4].
-== Enhancements we need ==
+[http://twitter.com/SarupBanskota Sarup] joined in 2013, Design Hub grew to GlitterGallery and went from idea to prototype. Sarup presented GlitterGallery, at the 2014 edition of the Libre Graphics Meeting held in Leipzig[4]. The proposal is to make GlitterGallery available for FLOSS designers to use, in a way that it fits into their workflow without involving much git-fu. In 2014, [https://twitter.com/RohitPaulK Rohit] joined GlitterGallery as a GSoC student. He worked on improving the project's Git-centric bits.
-=== Artwork ===
+There have been several contributors to the project since: https://github.com/glittergallery/GlitterGallery/graphs/contributors.
-* logo - something that reflects that we collaborate on cloud, and that designers hang out here.
+[2] - https://mairin.wordpress.com/2010/02/13/random-idea-for-design-collaboration-tool/
-* cartoons that explain different actions
-** setting up GG on OpenShift
-** making a contribution to the codebase
-=== An awesome commenting system ===
+[3] - http://en.wikipedia.org/wiki/Libre_Graphics_Meeting
-Possibly the most important component of GlitterGallery is the way it helps understand feedback. It would be useful to be able to support a commenting system that both provides socialization to some extent, while providing a way to distinguish useful feedback from the rest.
+[4] - http://libregraphicsmeeting.org/2012/
-Things to work on in this direction:
+[5] - http://libregraphicsmeeting.org/2014/
-* Likes/+1s/Upvotes for the comments. We need this to be implemented in a way that the entire page doesn't need a refresh.
-* Threaded replies - let people reply to replies and so on.
-* Mardown editor: currently, the comments support markdown, it will be really useful to provide with buttons to press for people who aren't used to writing in markdown. This feature can also be carried over to Glitterposts.
-* Mark as issue: this is a very important area to improve on. It would be useful for the author of the project to be able to mark a particular comment as an issue - this could be transferred into the tracker for someone to work on.
-* Overall UI - make the comment boxes expand as the user enters the comment, etc. Enable easy identification of project owner through tags or differently colored comment boxes.
-* Allow references from commit pages etc
-=== An issue tracker that works in sync with the commenting system ===
+== Talks & Coverage ==
+Over time, GlitterGallery has been discussed at various events where other Fedora folk have been present.
-Things to work on in this direction:
+{| border="1" align="center"
-* Sync comments to issues. When a user reports a comment as an issue, maybe it's a good idea to ask the user for some more information about the comment before checking it in as an issue, or maybe it isn't. Think what would be better in terms of UX.
+! Contributor !! Event !! Location !! Type of coverage !! Relevant Links
-* Allow project owners to let people take up issues.
+|-
-* Allow refences on commits/pull requests, just like GitHub does.
+| [[User:Emichan | Emily Dirsh]], [[User: Duffy | Máirín Duffy]] || Libre Graphics Meeting 2012 || Vienna || Talk || [https://www.youtube.com/watch?v=3sgbJVqBLpQ Video]
-* Integrate this with the user's email and in future, the GG notification system.
+|-
+| [[User:Sarupbanskota | Sarup Banskota]] || FOSSASIA 2014 || Phnom Penh || Talk || [http://www.slideshare.net/sarupbanskota/sarup-fossasia slides]
+|-
+| [[User:Sarupbanskota | Sarup Banskota]] || Libre Graphics Meeting 2014 || Leipzig || Talk || [http://download.gimp.org/pub/gimp/lgm/2014/day_4/065_GlitterGallery__Taking_the_designers_office_online/065_GlitterGallery__Taking_the_designers_office_online.ogv Video], [http://www.slideshare.net/sarupbanskota/helloworld-33181550 slides], [http://commonsmachinery.se/2014/03/metadata-handling-in-some-projects-at-lgm2014/ commonsmachinery], [http://www.shuttleworthfoundation.org/metadata-handling-in-some-projects-at-lgm2014/ shuttleworthfoundation], [http://lwn.net/Articles/496375/ lwn]
+|}
-=== Socialization ===
+== Fedora Design Team Installation ==
-Socialization is useful for people to be able to use the application effectively. While we don't intend to waste people's time by providing unnecessary feature sets, a minimum amount of socialization can go a long way in improving the overall design of the product.
+A link to a working deployment will be always available on the GlitterGallery README[6].
-Things to work on in this direction:
+[6] - https://github.com/glittergallery/GlitterGallery/blob/master/README.markdown
-* Allow users to follow people, so they receive updates about their activity
-* Allow users to follow projects, so they receive updates about progress of the project
-* Notification system - for project owners to realize about pull requests etc
-* Feed - that gives people updates from people & projects they follow
-* Email integration - send out emails when new issues are reported, or when new pull requests are offered
-=== Improved login ===
+== Meetings ==
-* Allow people to login through social media such as Facebook or Twitter
+We try to have weekly meetings every Wednesday on #glittergallery at Freenode.
-* Provide admininstrators with the option of only providing the kind of logins they allow
-=== Better integration with Git ===
+== Communication ==
-* The forking/merging process are currently ugly hacks that can be optimized through some code made available by the grit library
+Like/hate anything in particular? Just ping one of us and we'll follow up!
-* GitHub seems to be moving to rugged, do we need to make the switch too?
-=== User Interface / Overall visual appeal ===
+*Sarup: sarup AT glittergallery DOT net [http://sarupbanskota.github.io Blog]
+*Rohit: rohitkuruvilla AT yahoo DOT co DOT in [https://roon.io/rohitpaulk Blog]
+*Emily: edirsh AT redhat DOT com
-We need serious help improving the overall UI of GlitterGallery. If HTML/Stylesheets/JS are your comfort zone, you can be of a lot of help! We currently need help with getting over the hacky design. We've cleaned up quite a bit and GlitterGallery is fairly usable, but it lacks visual appeal.
+== Further links ==
-These are things you could get immediately involved with:
-* Typography - the fonts currently in use are nice, but we'd probably benefit from something more simple
-* color scheme - the color scheme has come a long way from the original pale one, but there's lots of room for improvement
-* Interactions - JS ninja? We need all of those sliding panels, smooth transitions and dynamism that web apps can't do without today, too!
-* Markup/layout - we need to layout our content better - does the idea of converting sketch mockups to working html interest you?
-=== Backend ===
+[1] - Wiki: https://github.com/glittergallery/GlitterGallery/wiki
-Whether you're new to programming, intermediate honing your skills, or a serious rubyist, we can use your help. Some areas you can contribute to right away:
+[2] - Mo's blog - https://mairin.wordpress.com/2010/02/13/random-idea-for-design-collaboration-tool/
-* Issue tracker - we're trying to build something similar to Bugzilla, but lightweight and minimal.
-* Socialization - everything from authentication to notifications to newsfeeds
-* Integrate grit better - love git? Now help GlitterGallery's backend use it better!
-=== Tests ===
+[3] - LGM Wikipedia - http://en.wikipedia.org/wiki/Libre_Graphics_Meeting
-With features being added everyday, our test suites need improvement!
+[4] - LGM 2012, Vienna - http://libregraphicsmeeting.org/2012/
-* Are you writing rspec tests? If yes, please help us improve ours or add new ones.
-* Are you a designer? It would be great if you could use what currently exists and report issues!
-* Are you a maintainer of a design team? We'll help you set up an instance of GlitterGallery for you.
-== Communication ==
+[5] - LGM 2014, Leipzig - http://libregraphicsmeeting.org/2014/
-Like/hate anything in particular? Let us know, we're just an email away! Just ping Sarup, he's always looking for someone to chat with during the afternoon classes. You could also just open up questions as issues on the GitHub page
+[6] - README - https://github.com/glittergallery/GlitterGallery/blob/master/README.markdown
-* Twitter: @SarupBanskota
-* email: sarup AT glittergallery DOT net
-* GitHub: https://github.com/glittergallery/GlitterGallery

Search