Re: [Design-team] Github Repos

[Máirín Duffy]

maybe archival stuff is best stored in the shared drive bc nobody is going to want to git
clone a huge archive (the story of our current fedora hosted git repo) and if it's a
one off thing that is done and over with its not going to change so version control isnt
really useful at that point.

missed usecase is our ux projects which i think should be one repo per project so the devs
and contribs can just check out the repos for the projects they actually work on.

~m

Sent from my phone, which is not an iphone.

<div>-------- Original message --------</div><div>From: Emily Dirsh
<emichan(a)fedoraproject.org&gt; </div><div>Date:01/21/2015  5:28 PM 
(GMT-05:00) </div><div>To: Fedora Design Team
<design-team(a)lists.fedoraproject.org&gt; </div><div>Subject: Re:
[Design-team] Github Repos </div><div>
</div>I think we should consider a use case approach. A few use cases off the top of
my head:
- sharing common resources like inkscape templates
- collaborating on the wallpaper or another project
- collecting safe-to-use photos/illustrations for the magazine
- archiving old artwork for inspiration or potential reuse (but without a specific need)
- distributing fedora logos to team members

I'm sure there are others I'm not considering right now.

It might help to list out the kind of things we want to include, but then think about
_why_ we want to include them when figuring out how to organize it all into specific
repos. That way, for our most common use cases, we can set up repos where you can clone a
repo and get everything you need, while minimizing what you don't need.

As far as the banner ad you mentioned, IMO it should go in the repo, but I think the use
case would be archival more than anything else.

- em




On Wed, Jan 21, 2015 at 3:43 PM, Ryan Lerch <rlerch(a)redhat.com&gt; wrote:
Hi all,

Just wondering if anyone has any ideas / thoughts on how we should organize the repos for
all our assets in github.

It might be worth trying to create a list of the assets / tasks that might be stored in
there, so we can come up with some guidelines on when and how to create new repos.

Some things to consider are small one-off tasks like this one i just completed:
https://fedorahosted.org/design-team/ticket/324

This is a kind of one-off task, but do we want to store this in git as well, just to keep
everything in the same place?

cheers,
ryanlerch
_______________________________________________
design-team mailing list
design-team(a)lists.fedoraproject.org
https://lists.fedoraproject.org/mailman/listinfo/design-team

Github Repos

[Emily Dirsh]

On Wed, Jan 21, 2015 at 8:11 PM, Máirín Duffy <duffy(a)fedoraproject.org&gt;
wrote:

>  maybe archival stuff is best stored in the shared drive bc nobody is
> going
>  to want to git clone a huge archive (the story of our current fedora hosted
>  git repo) and if it's a one off thing that is done and over with its not
>  going to change so version control isnt really useful at that point.
>  
Good point. Just need to make sure the shared drive is visible to the team
so people actually use it. :)


>  missed usecase is our ux projects which i think should be one repo
> per
>  project so the devs and contribs can just check out the repos for the
>  projects they actually work on.
>  
Agreed.

It might also be helpful to have a specific naming convention to
distinguish ux project repos from artwork project repos - i.e.
projectname-ux, or something like that.


>  ~m
>
>  Sent from my phone, which is not an iphone.
>
>
>  -------- Original message --------
>  From: Emily Dirsh
>  Date:01/21/2015 5:28 PM (GMT-05:00)
>  To: Fedora Design Team
>  Subject: Re: [Design-team] Github Repos
>
>  I think we should consider a use case approach. A few use cases off the
>  top of my head:
>  - sharing common resources like inkscape templates
>  - collaborating on the wallpaper or another project
>  - collecting safe-to-use photos/illustrations for the magazine
>  - archiving old artwork for inspiration or potential reuse (but without a
>  specific need)
>  - distributing fedora logos to team members
>
>  I'm sure there are others I'm not considering right now.
>
>  It might help to list out the kind of things we want to include, but then
>  think about _why_ we want to include them when figuring out how to organize
>  it all into specific repos. That way, for our most common use cases, we can
>  set up repos where you can clone a repo and get everything you need, while
>  minimizing what you don't need.
>
>  As far as the banner ad you mentioned, IMO it should go in the repo, but I
>  think the use case would be archival more than anything else.
>
>  - em
>
>
>
>
>  On Wed, Jan 21, 2015 at 3:43 PM, Ryan Lerch <rlerch(a)redhat.com&gt; wrote:
>
> > Hi all,
> >
> > Just wondering if anyone has any ideas / thoughts on how we should
> > organize the repos for all our assets in github.
> >
> > It might be worth trying to create a list of the assets / tasks that
> > might be stored in there, so we can come up with some guidelines on when
> > and how to create new repos.
> >
> > Some things to consider are small one-off tasks like this one i just
> > completed:
> > https://fedorahosted.org/design-team/ticket/324
> >
> > This is a kind of one-off task, but do we want to store this in git as
> > well, just to keep everything in the same place?
> >
> > cheers,
> > ryanlerch
> > _______________________________________________
> > design-team mailing list
> > design-team(a)lists.fedoraproject.org
> > https://lists.fedoraproject.org/mailman/listinfo/design-team
>
>
>
>  _______________________________________________
>  design-team mailing list
>  design-team(a)lists.fedoraproject.org
>  https://lists.fedoraproject.org/mailman/listinfo/design-team
>

Github Repos

[Máirín Duffy]

On 01/22/2015 10:23 AM, Emily Dirsh wrote:
>  Good point. Just need to make sure the shared drive is visible to
> the
>  team so people actually use it. :) 
I wonder if Luya could set up the Design Suite to automagically set up a 
nautilus bookmark to the shared drive so folks would just have to put 
their username/pass the first time they use it and then hopefully it'd 
be stored after that?

>      missed usecase is our ux projects which i think should be one
> repo
>      per project so the devs and contribs can just check out the repos
>      for the projects they actually work on.
>
>
>  Agreed.
>
>  It might also be helpful to have a specific naming convention to
>  distinguish ux project repos from artwork project repos - i.e.
>  projectname-ux, or something like that. 
great idea. if we made it ux-* then it'd be easier to sort by and all 
the ux repos would be grouped together in the end user's file manager.

~m

Github Repos

[Zoltan Hoppar]

Hi,

I have also an idea - what would be if we use our infra for hosting.
We have an amazing fedora hosted and we have copr. How about grouping
the resources and give an ability to reach them through copr. Of
course - what is legal protected stays within the team resources, but
otherwise we need some kind of public resources that every region can
use, or reuse.

Zoltan

2015-01-22 16:30 GMT+01:00 Máirín Duffy <duffy(a)fedoraproject.org&gt;:
>  On 01/22/2015 10:23 AM, Emily Dirsh wrote:
> >
> > Good point. Just need to make sure the shared drive is visible to the
> > team so people actually use it. :)
>
>
>  I wonder if Luya could set up the Design Suite to automagically set up a
>  nautilus bookmark to the shared drive so folks would just have to put their
>  username/pass the first time they use it and then hopefully it'd be stored
>  after that?
>
> >     missed usecase is our ux projects which i think should be one repo
> >     per project so the devs and contribs can just check out the repos
> >     for the projects they actually work on.
> >
> >
> > Agreed.
> >
> > It might also be helpful to have a specific naming convention to
> > distinguish ux project repos from artwork project repos - i.e.
> > projectname-ux, or something like that.
>
>
>  great idea. if we made it ux-* then it'd be easier to sort by and all the ux
>  repos would be grouped together in the end user's file manager.
>
>  ~m
>
>  _______________________________________________
>  design-team mailing list
>  design-team(a)lists.fedoraproject.org
>  https://lists.fedoraproject.org/mailman/listinfo/design-team 


-- 
PGP:  06853DF7

Github Repos

[Emily Dirsh]

On Thu, Jan 22, 2015 at 10:30 AM, Máirín Duffy <duffy(a)fedoraproject.org&gt;
wrote:

>  On 01/22/2015 10:23 AM, Emily Dirsh wrote:
>
> > Good point. Just need to make sure the shared drive is visible to the
> > team so people actually use it. :)
> >
>
>  I wonder if Luya could set up the Design Suite to automagically set up a
>  nautilus bookmark to the shared drive so folks would just have to put their
>  username/pass the first time they use it and then hopefully it'd be stored
>  after that?
>  
This would be great!


>       missed usecase is our ux projects which i think should be one repo
> >     per project so the devs and contribs can just check out the repos
> >     for the projects they actually work on.
> >
> >
> > Agreed.
> >
> > It might also be helpful to have a specific naming convention to
> > distinguish ux project repos from artwork project repos - i.e.
> > projectname-ux, or something like that.
> >
>
>  great idea. if we made it ux-* then it'd be easier to sort by and all the
>  ux repos would be grouped together in the end user's file manager.
>  
I like it! Should make it easier to search for UX related stuff, too.


>  ~m
>
>  _______________________________________________
>  design-team mailing list
>  design-team(a)lists.fedoraproject.org
>  https://lists.fedoraproject.org/mailman/listinfo/design-team
>