Re: FAD for websites

2016-12-11 Thread Alex Irmel Oviedo Solis 
Hello Robert, we call "fedora weekends" to our events, because these are at
fridays afternoon or saturdays morning by 3 or 4 hours.

We are at GMT-5 timezone, I think you are 6 hours in advance.

I can talk about basic topics for the first session like:

   - How to join to websites team (Read the wiki page, FAS account
   creation, send self introduction emails, etc)
   - Introduction to git.
   - Introduction to pagure.
   - Other topics can you suggest.

For the next sessions, we can talk about some specific topics like code
styling, tools, etc via bluejeans sessions as you suggested with some
easyfixes and a big job(for F26-Beta release) for the last session.

Best Regards.

El dom., 11 dic. 2016 a las 9:26, Robert Mayr ()
escribió:

2016-12-11 1:03 GMT+01:00 Alex Irmel Oviedo Solis :

Hello Robert, by now I'm 4 people interested to join to websites group.
Previously I maked little events named "Fedora weekends" oriented to design
with few people, I think we can organize 2 o 3 fedora weekends via hangouts
and in the last session we can do the easyfixes and review these to join
the people officially to the team. In the future we can make little local
FAD's and hacklab in the FUDCon/Flock event with these people.

If you are agreet we can make the first weekend in january.

Regards





Hi Alex,
this sounds like a good plan for me, although I'd organize this more like a
workshop and try to get feedback also between sessions, like the Infra guys
are doing.
January is ok for me, but we need to:

1) Find a suitable time to make the hangout session (I am UTC+1) of let's
say 2 hours? I cannot do a session for a whole weekend, sorry.
2) We could ask a RedHat guy to open a bluejeans session for us, which by
personal experience works much better for things like that
3) I would not make more than 3 sessions, maybe weekly
4) 3 weeks are too much for easyfix tickets, we can work on something
bigger together, which we can release for F26 Beta. Pagure makes it quite
easier to work on a separate project with forks and pull requests to a
dedicated branch.
5) It is fine to do easyfix stuff in the last session or shortly after it
and get people involved directly to the websites team (we can see how it
goes and maybe sponsor some of them even before)

The first steps to do first, IMO are:
a) start a "whenisgood" at the end of December to see when we can make the
workshops happen. If we want to use bluejeans I can try to organize the
session (or maybe Matthew also continues reading the topic ;)
b) People interested should at least read our wiki and clone the websites
repo. Reading something about git would also not harm :)

Other ideas? Would this work for you? If needed we can also organize a
websites meeting on IRC to discuss the details, just tell me.
Thanks again for your proposal and interest.
Kind regards.

-- 
Robert Mayr
(robyduck)
___
websites mailing list -- websites@lists.fedoraproject.org
To unsubscribe send an email to websites-le...@lists.fedoraproject.org

Re: FAD for websites

2016-12-11 Thread Robert Mayr 
2016-12-11 1:03 GMT+01:00 Alex Irmel Oviedo Solis :

> Hello Robert, by now I'm 4 people interested to join to websites group.
> Previously I maked little events named "Fedora weekends" oriented to design
> with few people, I think we can organize 2 o 3 fedora weekends via hangouts
> and in the last session we can do the easyfixes and review these to join
> the people officially to the team. In the future we can make little local
> FAD's and hacklab in the FUDCon/Flock event with these people.
>
> If you are agreet we can make the first weekend in january.
>
> Regards
>
>
>>
>>

Hi Alex,
this sounds like a good plan for me, although I'd organize this more like a
workshop and try to get feedback also between sessions, like the Infra guys
are doing.
January is ok for me, but we need to:

1) Find a suitable time to make the hangout session (I am UTC+1) of let's
say 2 hours? I cannot do a session for a whole weekend, sorry.
2) We could ask a RedHat guy to open a bluejeans session for us, which by
personal experience works much better for things like that
3) I would not make more than 3 sessions, maybe weekly
4) 3 weeks are too much for easyfix tickets, we can work on something
bigger together, which we can release for F26 Beta. Pagure makes it quite
easier to work on a separate project with forks and pull requests to a
dedicated branch.
5) It is fine to do easyfix stuff in the last session or shortly after it
and get people involved directly to the websites team (we can see how it
goes and maybe sponsor some of them even before)

The first steps to do first, IMO are:
a) start a "whenisgood" at the end of December to see when we can make the
workshops happen. If we want to use bluejeans I can try to organize the
session (or maybe Matthew also continues reading the topic ;)
b) People interested should at least read our wiki and clone the websites
repo. Reading something about git would also not harm :)

Other ideas? Would this work for you? If needed we can also organize a
websites meeting on IRC to discuss the details, just tell me.
Thanks again for your proposal and interest.
Kind regards.

-- 
Robert Mayr
(robyduck)
___
websites mailing list -- websites@lists.fedoraproject.org
To unsubscribe send an email to websites-le...@lists.fedoraproject.org