Attendees
Agenda/Notes
- Fedora 6 Testing
NLM: Getting F6 up and running in a production-like environment
MySQL, installed on a different server managed by database team
Connecting with different groups the organization
Starting functional and load testing
Andrew Woods has done some initial testing based on the test plan
- David to check in with Andrew on current status of testing and Fedora 6 feature tracking
- Feasibility of a "phone home" feature
- Discussed at the last Fedora Leaders meeting
- A feature that would allow Fedora to communicate with a central server to track implementations
- Some questions and concerns from the group
Would this be Opt-in or opt-out?
What does this mean for the different ways that people install Fedora?
Can we indicate in the Readme? Will people see it?
What about in a hosted environment?
How would this work in a Docker environment?
What guarantees do we have that this information would get to us?
If this is opt-in, how many people would use it?
People that opt-in would probably have already registered
Who are we going to tick off by having this feature?
How we can tell test vs. dev vs. production?
Maybe do an occasional ping to see if the server is alive
Ben: Initial reaction was an icky feeling
Doron: Potential security issue - sys admins asking why an application is sending out traffic
What kind of data do we want?
How can we make this data private/safe?
What about language barriers? Will people understand it?
Can we provide a service that people would want to register their Fedora repositories to get access to?
Update notification service. Releases, bug-fixes, etc.
This would still be a voluntary registration
What about value-add services
Follow ArchivesSpace model of providing services exclusively for members
Maybe make the change in association with Fedora 6 release
Messaging: We made it to Fedora 6 with dedicated community support, but the current membership model is not sustainable