Hey everybody, let's do a FAD!
We've had a lot of discussions about workflow, tooling, writing strategies, and shed paint since the last FAD, but our situation wrt publishing has not changed. It's time that we get together, find a room, and lock the door until a solution presents itself.
To that end, our friend shaunm has arranged for space at Red Hat Tower in Raleigh over the first weekend in May. Shaun has thoughtfully *also* invided other Docs folks from the Fedora ecosystem; this FAD[1] will give Fedora, CentOS, and Red Hat writers an opportunity to compare notes, workflows, etc with the goal of combining efforts and sharing content effectively.
The agenda still needs work, but I think our recent list discussions frame the intent nicely. We need to make room for modularized content, and doing so enables both contribution and consumption.
If you can provide a strong contribution towards solving this problem, please consider attending the FAD. Visit the wiki page, put your name on the list, and make sure to hit the table in the Budget section if you need funding. If you can't make it, we may be able to set up remote participation, or you can at least add your thoughts to the gestalt via the agenda or list.
-- Pete Travis Fedora Docs Project Lead
On Wed, 06 Apr 2016 13:34:40 -0500 Pete Travis me@petetravis.com wrote:
Hey everybody, let's do a FAD!
We've had a lot of discussions about workflow, tooling, writing strategies, and shed paint since the last FAD, but our situation wrt publishing has not changed. It's time that we get together, find a room, and lock the door until a solution presents itself.
To that end, our friend shaunm has arranged for space at Red Hat Tower in Raleigh over the first weekend in May. Shaun has thoughtfully *also* invided other Docs folks from the Fedora ecosystem; this FAD[1] will give Fedora, CentOS, and Red Hat writers an opportunity to compare notes, workflows, etc with the goal of combining efforts and sharing content effectively.
The agenda still needs work, but I think our recent list discussions frame the intent nicely. We need to make room for modularized content, and doing so enables both contribution and consumption.
If you can provide a strong contribution towards solving this problem, please consider attending the FAD. Visit the wiki page, put your name on the list, and make sure to hit the table in the Budget section if you need funding. If you can't make it, we may be able to set up remote participation, or you can at least add your thoughts to the gestalt via the agenda or list.
I don't know that I would be able to attend or be needed in person, but I would be very happy to participate remotely from the infrastructure side of things. I think whatever setup we go with needs to be something we are willing to deploy/maintain in infrastructure as well as all the other requirements. ;)
kevin
On 04/07/2016 12:55 PM, Kevin Fenzi wrote:
On Wed, 06 Apr 2016 13:34:40 -0500 Pete Travis me@petetravis.com wrote:
Hey everybody, let's do a FAD!
We've had a lot of discussions about workflow, tooling, writing strategies, and shed paint since the last FAD, but our situation wrt publishing has not changed. It's time that we get together, find a room, and lock the door until a solution presents itself.
To that end, our friend shaunm has arranged for space at Red Hat Tower in Raleigh over the first weekend in May. Shaun has thoughtfully *also* invided other Docs folks from the Fedora ecosystem; this FAD[1] will give Fedora, CentOS, and Red Hat writers an opportunity to compare notes, workflows, etc with the goal of combining efforts and sharing content effectively.
The agenda still needs work, but I think our recent list discussions frame the intent nicely. We need to make room for modularized content, and doing so enables both contribution and consumption.
If you can provide a strong contribution towards solving this problem, please consider attending the FAD. Visit the wiki page, put your name on the list, and make sure to hit the table in the Budget section if you need funding. If you can't make it, we may be able to set up remote participation, or you can at least add your thoughts to the gestalt via the agenda or list.
I don't know that I would be able to attend or be needed in person, but I would be very happy to participate remotely from the infrastructure side of things. I think whatever setup we go with needs to be something we are willing to deploy/maintain in infrastructure as well as all the other requirements. ;)
kevin
-- docs mailing list docs@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/docs@lists.fedoraproject.org
I would also like to attend remotely if possible. I cannot make it but would like to contribute in some manner.
Thank you, -Glen
On Apr 7, 2016 12:55, "Kevin Fenzi" kevin@scrye.com wrote:
On Wed, 06 Apr 2016 13:34:40 -0500 Pete Travis me@petetravis.com wrote:
Hey everybody, let's do a FAD!
snip
I don't know that I would be able to attend or be needed in person, but I would be very happy to participate remotely from the infrastructure side of things. I think whatever setup we go with needs to be something we are willing to deploy/maintain in infrastructure as well as all the other requirements. ;)
kevin
Sounds great. We would have questions for infra I'd probably take to you in any case :)
Someone should be able to set up bluejeans in the room, although I don't know if that can happen in advance or on the fly. Shawn and I were just chatting about remote participation, and are thinking of working some topical remote conference sessions into the agenda. We'll try to make those focused enough to make efficient use of your time.
-- Pete
On Fri, Apr 08, 2016 at 12:02:53PM -0500, Pete Travis wrote:
On Apr 7, 2016 12:55, "Kevin Fenzi" kevin@scrye.com wrote:
On Wed, 06 Apr 2016 13:34:40 -0500 Pete Travis me@petetravis.com wrote:
Hey everybody, let's do a FAD!
snip
I don't know that I would be able to attend or be needed in person, but I would be very happy to participate remotely from the infrastructure side of things. I think whatever setup we go with needs to be something we are willing to deploy/maintain in infrastructure as well as all the other requirements. ;)
Sounds great. We would have questions for infra I'd probably take to you in any case :)
+1; much appreciated, Kevin.
Someone should be able to set up bluejeans in the room, although I don't know if that can happen in advance or on the fly. Shawn and I were just chatting about remote participation, and are thinking of working some topical remote conference sessions into the agenda. We'll try to make those focused enough to make efficient use of your time.
I'm definitely interested and already signed up on the page. Jared told me he was ready and willing to go, too.
It should be easy to make Blue Jeans happen on the fly. I reserved a room for the whole weekend, and since we'd be there starting Friday, if anything's a problem we can get it fixed while there's support staff in the building.
Consider me keen!
Would be great to figure this out!
cheers, ryanlerch
On Thu, Apr 7, 2016 at 4:34 AM, Pete Travis me@petetravis.com wrote:
Hey everybody, let's do a FAD!
We've had a lot of discussions about workflow, tooling, writing strategies, and shed paint since the last FAD, but our situation wrt publishing has not changed. It's time that we get together, find a room, and lock the door until a solution presents itself.
To that end, our friend shaunm has arranged for space at Red Hat Tower in Raleigh over the first weekend in May. Shaun has thoughtfully *also* invided other Docs folks from the Fedora ecosystem; this FAD[1] will give Fedora, CentOS, and Red Hat writers an opportunity to compare notes, workflows, etc with the goal of combining efforts and sharing content effectively.
The agenda still needs work, but I think our recent list discussions frame the intent nicely. We need to make room for modularized content, and doing so enables both contribution and consumption.
If you can provide a strong contribution towards solving this problem, please consider attending the FAD. Visit the wiki page, put your name on the list, and make sure to hit the table in the Budget section if you need funding. If you can't make it, we may be able to set up remote participation, or you can at least add your thoughts to the gestalt via the agenda or list.
-- Pete Travis Fedora Docs Project Lead
[1] https://fedoraproject.org/wiki/FAD_Documentation_2016
docs mailing list docs@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/docs@lists.fedoraproject.org
On 04/06/2016 08:34 PM, Pete Travis wrote:
Hey everybody, let's do a FAD!
We've had a lot of discussions about workflow, tooling, writing strategies, and shed paint since the last FAD, but our situation wrt publishing has not changed. It's time that we get together, find a room, and lock the door until a solution presents itself.
To that end, our friend shaunm has arranged for space at Red Hat Tower in Raleigh over the first weekend in May. Shaun has thoughtfully *also* invided other Docs folks from the Fedora ecosystem; this FAD[1] will give Fedora, CentOS, and Red Hat writers an opportunity to compare notes, workflows, etc with the goal of combining efforts and sharing content effectively.
The agenda still needs work, but I think our recent list discussions frame the intent nicely. We need to make room for modularized content, and doing so enables both contribution and consumption.
If you can provide a strong contribution towards solving this problem, please consider attending the FAD. Visit the wiki page, put your name on the list, and make sure to hit the table in the Budget section if you need funding. If you can't make it, we may be able to set up remote participation, or you can at least add your thoughts to the gestalt via the agenda or list.
-- Pete Travis Fedora Docs Project Lead
[1] https://fedoraproject.org/wiki/FAD_Documentation_2016
docs mailing list docs@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/docs@lists.fedoraproject.org
Unfortunately I will be traveling that weekend, holiday already booked.
StephenW in Brno
I'll also be traveling that weekend and hope that the sessions will be recorded or there will be a good report out quickly afterward.
regrads,
bex
On 04/08/2016 10:14 AM, Stephen Wadeley wrote:
On 04/06/2016 08:34 PM, Pete Travis wrote:
Hey everybody, let's do a FAD!
We've had a lot of discussions about workflow, tooling, writing strategies, and shed paint since the last FAD, but our situation wrt publishing has not changed. It's time that we get together, find a room, and lock the door until a solution presents itself.
To that end, our friend shaunm has arranged for space at Red Hat Tower in Raleigh over the first weekend in May. Shaun has thoughtfully *also* invided other Docs folks from the Fedora ecosystem; this FAD[1] will give Fedora, CentOS, and Red Hat writers an opportunity to compare notes, workflows, etc with the goal of combining efforts and sharing content effectively.
The agenda still needs work, but I think our recent list discussions frame the intent nicely. We need to make room for modularized content, and doing so enables both contribution and consumption.
If you can provide a strong contribution towards solving this problem, please consider attending the FAD. Visit the wiki page, put your name on the list, and make sure to hit the table in the Budget section if you need funding. If you can't make it, we may be able to set up remote participation, or you can at least add your thoughts to the gestalt via the agenda or list.
-- Pete Travis Fedora Docs Project Lead
[1] https://fedoraproject.org/wiki/FAD_Documentation_2016
docs mailing list docs@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/docs@lists.fedoraproject.org
Unfortunately I will be traveling that weekend, holiday already booked.
StephenW in Brno
docs mailing list docs@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/docs@lists.fedoraproject.org
On Tue, Apr 12, 2016 at 02:41:22PM +0200, Brian (bex) Exelbierd wrote:
I'll also be traveling that weekend and hope that the sessions will be recorded or there will be a good report out quickly afterward.
Remy and I care deeply (i.e. no different than others here) :-) about keeping the proceedings transparent to the entire community. You can count on us to provide prompt reporting. I'm hoping to actually do this on at least a daily basis, rather than waiting until afterward.
On Fri, Apr 15, 2016 at 05:40:02PM -0400, Paul W. Frields wrote:
On Tue, Apr 12, 2016 at 02:41:22PM +0200, Brian (bex) Exelbierd wrote:
I'll also be traveling that weekend and hope that the sessions will be recorded or there will be a good report out quickly afterward.
Remy and I care deeply (i.e. no different than others here) :-) about keeping the proceedings transparent to the entire community. You can count on us to provide prompt reporting. I'm hoping to actually do this on at least a daily basis, rather than waiting until afterward.
I wanted to give an update of sorts here as well as make some agenda suggestion. We could use this to guide the flow for the three days of the event. I think the purpose I laid out on the wiki page earlier doesn't give a good idea of how to cut up the time to make it as productive as possible.
https://fedoraproject.org/wiki/FAD_Documentation_2016
I'm not an expert at mapping out this kind of FAD, but since no one else has built the agenda, here's a starting point. I'm not looking to impose a heavy process here, and I would *strongly* discourage process mavens from bogging down that way. We want to keep ideas flowing and avoid ratholes.
The agenda gets wider/looser as it goes on. This is purposely to avoid running up against a clock at a critical point. It's OK if we finish some things early; conversely, if we run late, we have slack time to account for that.
We will have an audio dial-in posted on the FAD page shortly for remote folks who want to attend via phone. This room does not have built in video conferencing, but if that becomes necessary we can broadcast from a laptop.
* * * Friday, May 6 (all times in EDT, UTC-4)
The goal for day 1 is to figure out the workflows we need to support for the best possible engagement across all the people involved.
* 09:30am - Arrive at lobby at Red Hat Tower -- I'm working with Remy so we can get everyone into the building appropriately. We have the "Fedora" room on 9th floor reserved, which is publicly accessible. * 09:45am - Introductions, get acquainted * 10:00am - Go around the room and state your meeting goals, pain points, what skills/resources you bring to the FAD * 11:00am - Map out high level user stories (we may have some already) -- I would ask that we *AVOID* any talk about any specific tools, markup, or implementation until done with this * 12:30pm - Lunch * 02:00pm - Finish user stories * 04:00pm - Start discussing currently available tools and the user stories they either hit or miss * 05:30pm - end of day(ish), depending on how discussions go -- record a "report out" on activities for community transparency * 06:30pm - dinner somewhere TBD
Saturday, May 7
The goal for day 2 is to come to an agreement across all involved on the tools needed to achieve the workflows we described on day 1.
* 09:30am - convene, continue tools talk * 12:30pm - Lunch * 02:00pm - Ideally, we have reached a point we agree on a tools strategy. If not, this day continues until done! If so, we can move on to mapping out any system changes, infrastructure work, enhancements, or features that someone needs to create; and assign each of these with a due date to someone. * 06:00pm - end of day(ish) -- record "report out" * 07:00pm - dinner somewhere TBD
Sunday, May 8
The goal for day 3 is to hack on things while we're f2f. This should be done in a concerted, sprinty way (e.g. cards) to avoid getting off topic or otherwise wasting time.
On 05/02/2016 11:53 PM, Paul W. Frields wrote:
I'm not an expert at mapping out this kind of FAD, but since no one else has built the agenda, here's a starting point. I'm not looking to impose a heavy process here, and I would *strongly* discourage process mavens from bogging down that way. We want to keep ideas flowing and avoid ratholes.
The agenda gets wider/looser as it goes on. This is purposely to avoid running up against a clock at a critical point. It's OK if we finish some things early; conversely, if we run late, we have slack time to account for that.
We will have an audio dial-in posted on the FAD page shortly for remote folks who want to attend via phone. This room does not have built in video conferencing, but if that becomes necessary we can broadcast from a laptop.
Friday, May 6 (all times in EDT, UTC-4)
The goal for day 1 is to figure out the workflows we need to support for the best possible engagement across all the people involved.
- 09:30am - Arrive at lobby at Red Hat Tower -- I'm working with Remy so we can get everyone into the building appropriately. We have the "Fedora" room on 9th floor reserved, which is publicly accessible.
- 09:45am - Introductions, get acquainted
- 10:00am - Go around the room and state your meeting goals, pain points, what skills/resources you bring to the FAD
- 11:00am - Map out high level user stories (we may have some already) -- I would ask that we *AVOID* any talk about any specific tools, markup, or implementation until done with this
- 12:30pm - Lunch
- 02:00pm - Finish user stories
- 04:00pm - Start discussing currently available tools and the user stories they either hit or miss
This reads like a premature point to begin the introduction of a tools conversation.
Depending on the goals identified, I believe that discussing how (conceptually) to interconnect (without concern for tools) would be better. For example, if there is a desire to see greater shared content then a conversation around the type of content (i.e. Virtualization Documentation) and Format (i.e. How Tos, Articles, Books, etc.) would yield more value. This would seem to solidfy the what before trying to talk about the how.
- 05:30pm - end of day(ish), depending on how discussions go -- record a "report out" on activities for community transparency
- 06:30pm - dinner somewhere TBD
Saturday, May 7
The goal for day 2 is to come to an agreement across all involved on the tools needed to achieve the workflows we described on day 1.
- 09:30am - convene, continue tools talk
- 12:30pm - Lunch
- 02:00pm - Ideally, we have reached a point we agree on a tools strategy. If not, this day continues until done! If so, we can move on to mapping out any system changes, infrastructure work, enhancements, or features that someone needs to create; and assign each of these with a due date to someone.
- 06:00pm - end of day(ish) -- record "report out"
- 07:00pm - dinner somewhere TBD
Sunday, May 8
The goal for day 3 is to hack on things while we're f2f. This should be done in a concerted, sprinty way (e.g. cards) to avoid getting off topic or otherwise wasting time.
regards,
bex
On Wed, May 04, 2016 at 09:00:02AM +0200, Brian (bex) Exelbierd wrote:
On 05/02/2016 11:53 PM, Paul W. Frields wrote:
I'm not an expert at mapping out this kind of FAD, but since no one else has built the agenda, here's a starting point. I'm not looking to impose a heavy process here, and I would *strongly* discourage process mavens from bogging down that way. We want to keep ideas flowing and avoid ratholes.
The agenda gets wider/looser as it goes on. This is purposely to avoid running up against a clock at a critical point. It's OK if we finish some things early; conversely, if we run late, we have slack time to account for that.
We will have an audio dial-in posted on the FAD page shortly for remote folks who want to attend via phone. This room does not have built in video conferencing, but if that becomes necessary we can broadcast from a laptop.
Friday, May 6 (all times in EDT, UTC-4)
The goal for day 1 is to figure out the workflows we need to support for the best possible engagement across all the people involved.
- 09:30am - Arrive at lobby at Red Hat Tower -- I'm working with Remy so we can get everyone into the building appropriately. We have the "Fedora" room on 9th floor reserved, which is publicly accessible.
- 09:45am - Introductions, get acquainted
- 10:00am - Go around the room and state your meeting goals, pain points, what skills/resources you bring to the FAD
- 11:00am - Map out high level user stories (we may have some already) -- I would ask that we *AVOID* any talk about any specific tools, markup, or implementation until done with this
- 12:30pm - Lunch
- 02:00pm - Finish user stories
- 04:00pm - Start discussing currently available tools and the user stories they either hit or miss
This reads like a premature point to begin the introduction of a tools conversation.
Depending on the goals identified, I believe that discussing how (conceptually) to interconnect (without concern for tools) would be better. For example, if there is a desire to see greater shared content then a conversation around the type of content (i.e. Virtualization Documentation) and Format (i.e. How Tos, Articles, Books, etc.) would yield more value. This would seem to solidfy the what before trying to talk about the how.
You're right, but this is part of the intended goals of the user stories. "I'm a content consumer, and I expect/need to..." as well as "I'm an expert content writer, and I expect/need to..." are ways to find those answers.
There is a video recording of our report out from Day 1 of the FAD, here: https://bluejeans.com/s/9Bgg/
If anyone watches this and would like to join remotely, we have access information on the FAD wiki page so you can join starting tomorrow at 9:30am EDT tomorrow. Please drop by IRC #fedora-docs to let us know you're joining.
https://fedoraproject.org/wiki/FAD_Documentation_2016
Paul
On Thu, May 5, 2016 at 1:19 PM, Paul W. Frields stickster@gmail.com wrote:
On Wed, May 04, 2016 at 09:00:02AM +0200, Brian (bex) Exelbierd wrote:
On 05/02/2016 11:53 PM, Paul W. Frields wrote:
I'm not an expert at mapping out this kind of FAD, but since no one else has built the agenda, here's a starting point. I'm not looking to impose a heavy process here, and I would *strongly* discourage process mavens from bogging down that way. We want to keep ideas flowing and avoid ratholes.
The agenda gets wider/looser as it goes on. This is purposely to avoid running up against a clock at a critical point. It's OK if we finish some things early; conversely, if we run late, we have slack time to account for that.
We will have an audio dial-in posted on the FAD page shortly for remote folks who want to attend via phone. This room does not have built in video conferencing, but if that becomes necessary we can broadcast from a laptop.
Friday, May 6 (all times in EDT, UTC-4)
The goal for day 1 is to figure out the workflows we need to support for the best possible engagement across all the people involved.
- 09:30am - Arrive at lobby at Red Hat Tower -- I'm working with Remy so we can get everyone into the building appropriately. We have the "Fedora" room on 9th floor reserved, which is publicly accessible.
- 09:45am - Introductions, get acquainted
- 10:00am - Go around the room and state your meeting goals, pain points, what skills/resources you bring to the FAD
- 11:00am - Map out high level user stories (we may have some already) -- I would ask that we *AVOID* any talk about any specific tools, markup, or implementation until done with this
- 12:30pm - Lunch
- 02:00pm - Finish user stories
- 04:00pm - Start discussing currently available tools and the user stories they either hit or miss
This reads like a premature point to begin the introduction of a tools conversation.
Depending on the goals identified, I believe that discussing how (conceptually) to interconnect (without concern for tools) would be better. For example, if there is a desire to see greater shared content then a conversation around the type of content (i.e. Virtualization Documentation) and Format (i.e. How Tos, Articles, Books, etc.) would yield more value. This would seem to solidfy the what before trying to talk about the how.
You're right, but this is part of the intended goals of the user stories. "I'm a content consumer, and I expect/need to..." as well as "I'm an expert content writer, and I expect/need to..." are ways to find those answers.
-- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com
-
Brian Exelbierd -
Glen Rundblom -
Kevin Fenzi -
Paul W. Frields -
Pete Travis -
Ryan Lerch -
Stephen Wadeley