fedora-pgm / schedule

#220 Elections schedule change was not published and should not have been done directly here
Closed by amoloney. Opened by adamwill.

Closed
Reopen Issue

I notice that @jflory7 did a manual edit to the f43 elections schedule. There's a couple of problems with this.

One, just editing the files in this repo alone does nothing. The published schedule has not changed. That's because there's no automated process for publishing the schedule, it has to be done manually.

To do this you need permissions to rsync to fedorapeople.org:/project/schedule . If you have that, you can edit common/Makefile.common in your checkout of this repo to have your username not amoloney's (but remember not to commit that change!), then run make publish in the appropriate directory (f-43 in this case).

Two, changes aren't meant to be made directly here. They're meant to be made in RH's instance of smartsheet and exported as XML, then the exported XML file should be committed here. This is an awful system but it's the system we've got. Making edits manually here has two risks. One, if anyone else then goes and does a future update in smartsheet, your changes will likely get reversed. Two, it's easy to make mistakes or miss something when doing manual edits; the schedule files are quite complicated and often events are meant to have internal relationships to each other, or there are overarching events that depend on individual event dates or vice versa. It's easy to knock things 'out of sync' by making manual edits.

Hey @adamwill, thanks for opening this. I have been working on the modified Elections schedule, but I am starting to think that the modified F43 schedule will not get published before the year-end.

One, just editing the files in this repo alone does nothing. The published schedule has not changed. That's because there's no automated process for publishing the schedule, it has to be done manually.

To do this you need permissions to rsync to fedorapeople.org:/project/schedule . If you have that, you can edit common/Makefile.common in your checkout of this repo to have your username not amoloney's (but remember not to commit that change!), then run make publish in the appropriate directory (f-43 in this case).

These are all of the steps I have followed, and I do have access to the program-management FAS group now (see fedora-infrastructure#12962). However, I am still blocked on the make publish step because my FAS group does not have permissions to publish the change.

$ make publish
../pgm-build-fedora
Generating fpl
Generating upstream
Generating all
Generating devel
Generating quality
Generating docs
Generating workstation
Generating web
Generating pm
Generating trans
Generating releng
Generating mindshare
Generating key
Generating magazine
Generating design
Generating events
Generating infrastructure
Generating elections
Generating spins
sending incremental file list
f-43-all-tasks.html
f-43-design-tasks.html
f-43-devel-tasks.html
f-43-docs-tasks.html
f-43-elections-tasks.html
f-43-events-tasks.html
f-43-fpl-tasks.html
f-43-infrastructure-tasks.html
f-43-key-tasks.html
f-43-magazine-tasks.html
f-43-mindshare-tasks.html
f-43-pm-tasks.html
f-43-quality-tasks.html
f-43-releng-tasks.html
f-43-spins-tasks.html
f-43-trans-tasks.html
f-43-upstream-tasks.html
f-43-web-tasks.html
f-43-workstation-tasks.html
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-all-tasks.html.ippQxT" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-design-tasks.html.67ooa5" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-devel-tasks.html.KRUrZ9" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-docs-tasks.html.curRqd" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-elections-tasks.html.7Q3OTi" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-events-tasks.html.ygpwvJ" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-fpl-tasks.html.JNWIsW" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-infrastructure-tasks.html.ouzBcX" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-key-tasks.html.AVXUKR" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-magazine-tasks.html.BpXMpQ" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-mindshare-tasks.html.ctn0Tb" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-pm-tasks.html.isLkWu" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-quality-tasks.html.ApaJLt" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-releng-tasks.html.i9D7Gp" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-spins-tasks.html.oeKd04" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-trans-tasks.html.BiztiV" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-upstream-tasks.html.xEiDNl" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-web-tasks.html.M4HKfm" failed: Permission denied (13)
rsync: [receiver] mkstemp "/project/schedule/f-43/.f-43-workstation-tasks.html.l3iyQn" failed: Permission denied (13)
sent 16,001 bytes  received 2,135 bytes  4,030.22 bytes/sec
total size is 197,834  speedup is 10.91
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.4.1]
make: *** [../common/Makefile.common:31: publish] Error 23

Unfortunately, I do not have the time or bandwidth to debug this further. If someone else who has published the modified schedule is able to run make publish on the modified f-43/ directory, then we could at least get the "band-aid" fix for the F43 Elections cycle.

Two, changes aren't meant to be made directly here. They're meant to be made in RH's instance of smartsheet and exported as XML, then the exported XML file should be committed here. This is an awful system but it's the system we've got. Making edits manually here has two risks.

I am actually not sure who has the Smartsheets access here. I don't. I went for the manual change because I erred on the side that maybe I could force-publish the manual changes for the purpose of the next 1-2 weeks while the modified election schedule is in effect. However, I am a bit stuck here.

If the F43 schedule from Smartsheets rewrites the modified Elections schedule in 2026, that will be fine by me since the election will be over, and most people checking the schedule in 2026 won't care so much about what the dates were in the past tense.

@adamwill If you can run make publish here to get the band-aid fix deployed, that would be awesome!

@adamwill
this is actually mostly on me. I'm suppose to be covering for the schedule change stuff and I'm trying to sort this out without messing up the smartsheets stuff in a way that causes more problems.

Does this require any action now? Or can I go ahead and close it out?

Closing this as the dates seem to match up from the schedule and blog announcements.

Metadata Update from @amoloney:
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.