The way forward and Docs Meeting Minutes
by Brian Exelbierd
Here are the minutes from today's docs meeting. It was really just a
conversation about the way forward (see below):
<zodbot> Meeting ended Mon Jul 31 14:54:46 2017 UTC. Information about
MeetBot at http://wiki.debian.org/MeetBot .
<zodbot> Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2017-07-31/fedora_docs.2...
<zodbot> Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2017-07-31/fedora_docs.2...
<zodbot> Log:
https://meetbot.fedoraproject.org/fedora-meeting/2017-07-31/fedora_docs.2...
## The way forward
The proposed movement forward is this:
1. Fix https://pagure.io/docs-reboot/docs-fp-o/issue/5 - our only
blocker bug. x3mboy and rkratky are hoping to have a fix this week
unless someone beats them to it.
2. Create an html repo for publishing the new site.
3. Rename all existing docs repositories on pagure into a
fedora-docs-old namespace.
4. Rename the docs-reboot namespace fedora-docs and fix permissions on
repositories.
5. Work with infra to get the existing docs.fp.o site renamed to
docs-old.fp.o when the new site launches.
6. Prepare a final DocBook publish that removes the F26 materials from
the old site and push it when the new site launches (or shortly
thereafter). After this make publishing of this site a manual effort as
it should no longer get updates.
7. Work with infra to get the new docs.fp.o html repository publishing
on docs.fp.o and docs.stg.fp.o. Ideally we will have the shortest
refresh cycle possible for a while to permit rapid republishing in case
we find problems at launch.
8. Create a CI job in the CentOS CI that regenerates the site upon
updates to the branches. Today this is a manual step (3 commands or
so). Ideally this CI job will produce stage which can then be manually
merged to prod.
9. Begin work on phase II and any new bugs found. Phase II priorities
include Translation and Search. We should also work on any new content
that wishes to be published this way, including the content the council
wants to bring over. Far from lastly, we need a new content and a
contribution guide.
As the meeting was lightly attended but we have in principal agreed on
this move in the past, I am going to keep working with the team to drive
it forward. If there are questions please raise them now.
regards,
bex
6 years, 8 months
New Docs Site Update
by Brian Exelbierd
Warning: I forced push a bunch of commits to clean up some disasters. I
am a bad person who feels bad for this. If you have forks you will need
to do some force updating. I am sorry.
The docs test site reflects the latest build:
https://bex.fedorapeople.org/fedora-docs-web/
The next steps from here are to begin the roll out. No other blockers
have been reported.
In parallel Kristyna will be doing the following:
* Finding all doc repositories and working to get the old DocBook ones
into the name space fedora-docs-old and the new asciibinder ones into
fedora-docs (instead of docs-reboot).
* Working with Infra to:
- Get the existing docs.fp.o moved to docs-old.fp.o (stg will follow
the same convention)
- Mapping a new docs.fp.o to a new html repository for delivery
- Ideally getting more frequent stg and prod updates for the next few
months in hopes that we can push changes faster in case we find more
errors
Additionally, we need to work on the following (in no particular order)
- A CI job to build the site. A job that can be triggered by fedmsg
updates has been created in the CentOS CI but no configuration or job
script has been written. Kristyna and I should be able to get the basic
job configuration done. I think the Jenkins builder used by the budget
will be able to be repurposed for this. If you're interested in helping
with this let us know.
- Enabling translation support. This will involve pushing new AsciiDoc
sources to Zanata for what has changed and building a process to do this
regularly. The feedback from jibecfed needs to be incorporated and some
test sites built. This is process has been tested, but needs to be made
a reality. This will probably involve some shell scripting and some
perl code to update po4a.
- Document (and update the wiki) how to make updates to the English
documentation.
- Ensure that Translation has a known working process for requesting
translation publication updates.
Are we missing anything?
regards,
bex
6 years, 8 months
Docs Meeting - 21 August - New Site rolling out soon
by Brian Exelbierd
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2017-08-21/fedora-docs.2...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2017-08-21/fedora-docs.2...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2017-08-21/fedora-docs.2...
The big conversation was on getting the site actually live:
Roll Call (bexelbie, 14:01:20)
Pause for Emergency Coffee (bexelbie, 14:04:02)
Rolling out the New Docs System (bexelbie, 14:06:13)
https://bex.fedorapeople.org/fedora-docs-web/ (bexelbie,
14:07:25)
ACTION: bexelbie to try to migrate docs-reboot to fedora-docs
namespace. If that fails, x3mboy or kjandova__ will help with
opening a ticket to do it (bexelbie, 14:11:36)
ACTION: kjandova__ to open an infrastructure ticket (like this
one: https://pagure.io/fedora-infrastructure/issue/5973) to move
docs.fp.o to docs-old.fp.o and replace docs.fp.o and
docs.stg.fp.o with the new publishing repo from #1 (bexelbie,
14:12:07)
ACTION: kjandova__ to figure out which repos should be moved to
fedora-docs-old (bexelbie, 14:15:47)
https://pagure.io/group/fedora-docs (bexelbie, 14:19:03)
https://pagure.io/docs-reboot/system-administrators-guide <---
jhradilek (bexelbie, 14:21:08)
ACTION: bexelbie to make sure the fedora-docs group has access
to the new repos (bexelbie, 14:22:22)
ACTION: randomuser to prepare branch of web.git with only
content <F26 and new frontpage directing to new site
(randomuser, 14:26:34)
ACTION: bexelbie to update the new docs site front page with the
translation commment change from JB (bexelbie, 14:27:41)
What happens after all of this? (bexelbie, 14:31:17)
6 years, 8 months
Repository updates - new docs repos broke your old settings.
by Brian Exelbierd
I have migrated all the repositories over to pagure.io/fedora-docs/
You will need to reclone or force update any of your forks.
I broke JB's patch for the install-guide so I moved it over under my
name. I'll fix the crediting issue when we work on translations.
regards,
bex
6 years, 8 months
Memo
by Gary Skeete
Hello,
Within legal guidelines ,will payment to the Physician in this case myself Dr. Gary Skeete be from fee for service capitation or salary? -U.S.A
Canada -fee for service, primary care group payments, alternative payment plans.
All or some at least one of the aforementioned apply as an option.
The arrangements for my compensation should e made within this year with proper allowances for taxation forms and insurance papers should be filled out and copies sent to Dr. Gary Skeete
510-430 Mcmurchy Ave South
Brampton,Ontario,Canada
L6Y 2N4
All pay checks as well as stock options correspondence and future earnings such as royalties dividends and any monies donated can be sent to the above address.
Thank You
Dr.Gary Skeete
6 years, 8 months
Project Intention
by Gary Skeete
The collaboration between Aha Github and Datadog with help from Codeenvy Synapse.org Fedora Wordpress Facebook Codeschool Google Docs the collaboration between theoverall sciences of Mathematics Law and Medicine meeting the technologies of A.I. Cognitive computing and systems which Read text and interpret language to make plans for further code 3D printing engineering execution display and advantages in healthcare biomedical sciences results in Counterterrorisms and general safety precautions and regulations.
Anti crime as an institution the concepts that financially support factions of business corporate and industry the infrastructure that needs to safely support it and the people who keep the productivity engine going.
The aspect of researching new techniques as relayed in updates to Resuscitation non invasive surgery robotics and artificial intelligence as related to computational neuroscience and epigenetics as well as looking at the Watson computer at IBM for the discovery of new elements the function of which can be adjusted to suit innovation the aspect of earring and preventing disease viruses illnesses disorders all types of medical discrepancies the creation of concepts in scientific pursuit of mastery over nature the planet the universe and the never ending quest to listen and interpret God's word as a stable unifying force.
A source for peace unification and a smooth running planet due to empower,ent to unite against wrongdoings o create the prevention of the depevation of liberties and the subsequent turmoil by preventing the element of sin or doubt in that process of evolution in which grants us created in the image of God
6 years, 8 months
RE: Pagure or Bugzilla
by Ryan Gough
Hi all,
I'm personally in favour of Pagure because it puts bugs and docs in the
same location and I like that workflow as you can reference fixes directly
to the repo.
Regards,
Ryan
6 years, 8 months
Pagure or Bugzilla
by Brian Exelbierd
Hi All,
Which do we want to use for documentation bugs, Pagure Issues or
Bugzilla BZs?
If we aren't going to use Pagure Issues, I want to turn off the issues
for the repos and provide bug reporting guidance. By the same token, if
we aren't going to use BZs, I'd like to work with that team to see if we
can get some kind of forwarding or other solution to keep things from
getting lost.
My preferences is Issues at it puts bugs near the PRs, however there is
no requirement for this from my perspective. The negative is that I
believe you have to have a FAS (and possibly a +1) to report a Pagure
Issue, while only a lighterweight BZ account is required for Bugzilla.
That said, I think bugzilla is much harder for casual users to use.
We need opinions please.
regards,
bex
6 years, 8 months