fedora-join August 2016

fedora-join@lists.fedoraproject.org

10 participants
18 discussions

Re: [Community Operations (CommOps)] #80: Create 'wiki-editors' FAS group
by fedora-badges 09 Aug '16

09 Aug '16

#80: Create 'wiki-editors' FAS group --------------------------+------------------------- Reporter: jflory7 | Owner: jflory7 Type: enhancement | Status: accepted Priority: major | Milestone: ASAP Component: Outreach | Severity: urgent Resolution: | Keywords: nextmeeting --------------------------+------------------------- Comment (by yn1v): Replying to [comment:6 bt0dotninja]: > I suggest a low tech workaround: > > Designate a group's proxy for create/update "wiki user home page" under user request in group's mailing list, this will be part of the on-boarding process of the group.(we can use templates for convenience) > > Until the user has been accepted into the group can edit the wiki page (at this time will comply with CLA+1) > > as skamath said :"a spammer might not take the extra efforts to get boot-strapped into the group". this workaround will works for many groups (counterexample: Marketing, this people use the wiki a lot) > > It is my humble opinion. I am afraid of creating groups that are easy. As it was mentioned, it will award CLA+1 status, which means vote, fedorapeople space, mail alias, among other privileges. I am not sure if it is possible to create a group that does not count toward CLA+1. -- Ticket URL: <https://fedorahosted.org/fedora-commops/ticket/80#comment:15> Community Operations (CommOps) <https://fedoraproject.org/wiki/CommOps> Community Operations (CommOps) aims to build and improve community infrastructure to better communication across the Project and to help tell the story of Fedora.

1 0

Re: [Community Operations (CommOps)] #80: Create 'wiki-editors' FAS group
by fedora-badges 09 Aug '16

09 Aug '16

#80: Create 'wiki-editors' FAS group --------------------------+------------------------- Reporter: jflory7 | Owner: jflory7 Type: enhancement | Status: accepted Priority: major | Milestone: ASAP Component: Outreach | Severity: urgent Resolution: | Keywords: nextmeeting --------------------------+------------------------- Comment (by viorel): Replying to [comment:3 jflory7]: > I know the Ambassadors are one group that are affected by this, as it's a > pre-requisite that anyone looking to be involved as an Ambassador create > their user page with general info about them, why they want to get involved, > etc. The Ambassador mailing list is also only able to be posted to by > sponsored Ambassadors as well, which makes it difficult to defer > introductions to a mailing list. Most projects require a self-introduction email, any background on why Ambassadors chose wiki user page to come in before mailing list subscription? Replying to [comment:5 jflory7]: > It's a tough situation because on one hand, we're looking at potentially > making it more difficult to get a foothold in the project [...] Some projects clearly state on their join page the format for the self-introduction email. A new contributor can simply copy/paste that text and fill in the blanks which is as easy as (if not easier than) crafting a cool wiki page. While mailing lists can be spammed it seems to me that spamming a wiki is a much serious issue which makes admission to a project an absolute requirement to prevent defacing one of the public faces of Fedora. For that reason I'm a +1 for comment:12. -- Ticket URL: <https://fedorahosted.org/fedora-commops/ticket/80#comment:14> Community Operations (CommOps) <https://fedoraproject.org/wiki/CommOps> Community Operations (CommOps) aims to build and improve community infrastructure to better communication across the Project and to help tell the story of Fedora.

1 0

Re: [Community Operations (CommOps)] #80: Create 'wiki-editors' FAS group
by fedora-badges 08 Aug '16

08 Aug '16

1 0

Re: [Community Operations (CommOps)] #80: Create 'wiki-editors' FAS group
by fedora-badges 08 Aug '16

08 Aug '16

#80: Create 'wiki-editors' FAS group --------------------------+-------------------- Reporter: jflory7 | Owner: Type: enhancement | Status: new Priority: major | Milestone: ASAP Component: Outreach | Severity: urgent Resolution: | Keywords: --------------------------+-------------------- Comment (by jflory7): I think limiting the group to only user pages could be a good solution. I'm only partial to keeping a way in on the wiki for eager contributors because I recognize it as a lower-level bridge that can involve users / avid on-lookers with the project. There's also the Fedora common bugs wiki page, which is one way that someone can contribute to the project too, if they're not involved anywhere else. It's a tough situation because on one hand, we're looking at potentially making it more difficult to get a foothold in the project, but on the other hand, we have the issues with spam and having this turn into abuse very quickly. I'm also trying not to be overly biased since I personally feel like the wiki is a great way for people to become involved at the beginning, but that may just be how I see it. I'm trying to think of a good middle-of-the-road solution, but having a hard time thinking up something. I pinged a few others to take a look at this ticket, so perhaps some of the affected groups could weigh in on this topic as well. -- Ticket URL: <https://fedorahosted.org/fedora-commops/ticket/80#comment:5> Community Operations (CommOps) <https://fedoraproject.org/wiki/CommOps> Community Operations (CommOps) aims to build and improve community infrastructure to better communication across the Project and to help tell the story of Fedora.

1 0

Re: [Community Operations (CommOps)] #80: Create 'wiki-editors' FAS group
by fedora-badges 08 Aug '16

08 Aug '16

#80: Create 'wiki-editors' FAS group --------------------------+-------------------- Reporter: jflory7 | Owner: Type: enhancement | Status: new Priority: major | Milestone: ASAP Component: Outreach | Severity: urgent Resolution: | Keywords: --------------------------+-------------------- Comment (by bex): Perhaps the group should be restricted to creating user pages then? It just seems we made a decision to do this and now we are saying we want to either add more overhead or let anyone in and defeat the purpose. Skamath - my understanding is that we have had some very good social engineering done to us already on irc to get groups for spamming purposes. jflory7 - I realize your examples may not be exhaustive, but it sounds like only one group is impacted and they may be able to find an alternative. They may not. But then this should be somethign they need to manage as commops probably shouldn't be approving people for applications to ambassadors. -- Ticket URL: <https://fedorahosted.org/fedora-commops/ticket/80#comment:4> Community Operations (CommOps) <https://fedoraproject.org/wiki/CommOps> Community Operations (CommOps) aims to build and improve community infrastructure to better communication across the Project and to help tell the story of Fedora.

1 0

Re: [Community Operations (CommOps)] #80: Create 'wiki-editors' FAS group
by fedora-badges 08 Aug '16

08 Aug '16

#80: Create 'wiki-editors' FAS group --------------------------+-------------------- Reporter: jflory7 | Owner: Type: enhancement | Status: new Priority: major | Milestone: ASAP Component: Outreach | Severity: urgent Resolution: | Keywords: --------------------------+-------------------- Comment (by skamath): Replying to [comment:1 bex]: > I'd like to understand which groups need wiki editing privilege as a pre-requisite for group membership? Could those groups be asked to consider alternatives? This feels like we are setting ourselves up to get "social engineered" into inviting the spammers back. I feel otherwise. First of all, a spammer might not take the extra efforts to get boot-strapped into the group. Even if he/she does, basset would still detect the spam, delete the page and ban the user permanently. By having such a group, I believe we can take in only whom we think fits in. +1 from me. -- Ticket URL: <https://fedorahosted.org/fedora-commops/ticket/80#comment:2> Community Operations (CommOps) <https://fedoraproject.org/wiki/CommOps> Community Operations (CommOps) aims to build and improve community infrastructure to better communication across the Project and to help tell the story of Fedora.

1 0

Re: [Community Operations (CommOps)] #80: Create 'wiki-editors' FAS group
by fedora-badges 08 Aug '16

08 Aug '16

1 0

[Flock16] [Transcription] Fedora Hubs Meetup/Hackfest
by Justin W. Flory 05 Aug '16

05 Aug '16

These are the minutes from the Hubs workshop at Flock today. I'm sending this out to a couple of lists because I think it's something super interesting to multiple teams, and the summary (I feel) does a good job of explaining a complicated thing into common English. Enjoy! = = = = = Meeting ended Fri Aug 5 13:40:50 2016 UTC. Minutes: https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-05/flock2016.… Minutes (text): https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-05/flock2016.… Log: https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-05/flock2016.… * * * * * ========================================================================================== #fedora-flock-openqa: Fedora Hubs Meetup / Hackfest - Speaker: Pierre-Yves Chibon (pingou) ========================================================================================== Meeting started by jflory7 at 11:33:02 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-05/flock2016.… . Meeting summary --------------- * Getting ready / Introduction (jflory7, 11:33:16) * What is Hubs? (jflory7, 11:48:42) * Using fedmsg to capture all sorts of activities and information in Fedora (jflory7, 11:48:53) * Messages that cross over the bus all involve contributor activity - 1 thing with a problem (like other projects) is no easy way to connect people with teams that are of interest to them and resources they need to interact with these teams (jflory7, 11:50:19) * Systems we use to talk to contributors has their challenges: IRC is challenging but it's not something most people in the world are familiar with, have to get client, join channel, register with NickServ, etc. (same thing can go for mailing lists) (jflory7, 11:51:15) * Fedora Hubs brings together many systems that we use for communication and coordination and into a web-based view that quickly connects people to teams with people in there and what's happening in there (lowers the learning barrier) (jflory7, 11:51:52) * Use a widget to follow a discussion and writing a reply, monitor discussion, etc. (jflory7, 11:52:12) * Because we have fedmsg, we don't need to vent new channels and new activities that creates Balkanization problem of new vs. old contributors (jflory7, 11:52:50) * IDEA: Opening new views into existing systems (jflory7, 11:53:12) * Hubs is designed to not just be one arrangement, each team can have its own hub (jflory7, 11:53:24) * What do we want to do? (jflory7, 11:54:30) * LINK: https://pagure.io/fedora-hubs/issue/243 (mizmo, 11:55:35) * LINK: https://hubs-dev.fedorainfracloud.org (jflory7, 12:03:03) * LINK: https://hubs-dev.fedorainfracloud.org/skrzepto/ (skrzepto, 12:06:38) * === Widgets === (jflory7, 12:10:54) * Adding widget to hub: View your Hub in edit mode, choose your widget, add it, and configure it on the prompt right after (jflory7, 12:12:44) * Requesting a new meeting in Hubs creates a new meeting in Fedocal (jflory7, 12:16:04) * pkgdb: Seeing packages ready to be pushed to stable and other similar details in widgets (jflory7, 12:17:37) * Badges: View all of your badges (jflory7, 12:17:44) * Pagure: Newest open pull requests on Pagure tagged with fedora-infra tag (jflory7, 12:17:57) * Can also interact with GitHub and Bugzilla (other widgets coming from outside sources) (jflory7, 12:18:29) * IDEA: Avoiding silo of communications: Sticky note is maybe not a good idea because then it isolates those *not* using Hubs, so there could be separation of information that someone may miss if they are not on Hubs (jflory7, 12:19:39) * IDEA: WhenIsGood widget, but need to take caution on communication silos where it could separate the contributors who are and are not using Hubs (jflory7, 12:20:13) * === Hubs groups === (jflory7, 12:20:26) * LINK: https://hubs-dev.fedorainfracloud.org/designteam/ (mizmo, 12:21:45) * LINK: https://hubs-dev.fedorainfracloud.org/groups (jflory7, 12:22:54) * Able to have community rules and guidelines in a group hub, as well as meetings for schedule and past meeting minutes all from the main team widget (jflory7, 12:23:54) * HELP: Need more help on widgets, designing the hubs themselves for groups - design team has good representation with ryanlerch and mizmo, but we need more input and involvement with other groups and teams (jflory7, 12:25:29) * HELP: Packager needs help and input since it's a large group (jflory7, 12:25:49) * LINK: https://github.com/fedora-infra/zanata2fedmsg (jflory7, 12:26:16) * IRC widget in progress which allows you to view design team channel (a la Facebook Messenger style) on IRC, you can live chat with the folks you can see on the hub (jflory7, 12:27:21) * Q: "My personal hub... will people be able to see that?" (jflory7, 12:30:48) * A: Yes, but plan to get private and public side, e.g. your live feed, library widget, things from FAS (jflory7, 12:31:28) * Personal stream in development for saving things from your incoming stream for later reference (jflory7, 12:32:28) * === History of project === (jflory7, 12:32:48) * New Hubs superhero will be sayan for leading the project forward (jflory7, 12:33:54) * HELP: We need some assistance with the IRC widget with user use case, we're working with developers to developers - mockups would be helpful (jflory7, 12:35:47) * LINK: https://pagure.io/fedora-hubs/issues?tags=needsmockup (jflory7, 12:35:48) * === So what do we want to do moving forward? === (jflory7, 12:42:18) * LINK: https://pagure.io/fedora-hubs/issue/243 <= scavenger hunt, if anyone is up for a challenge (mizmo, 12:43:15) * Q: "Do you have a Vagrant set up for this?" (jflory7, 12:45:10) * A: No-yes? ryanlerch has something he has been working on as a work in progress, but needs some more visiting (jflory7, 12:45:47) * HELP: fedora-hubs#243 could use another pair of eyes (jflory7, 12:46:59) * Open hacking (jflory7, 12:50:10) * LINK: http://localhost:5000/designteam/ <= no problem (mizmo, 12:52:42) * LINK: http://localhost:5000/duffy/ <= oopsie (mizmo, 12:52:50) Meeting ended at 13:40:50 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jflory7 (156) * mizmo (47) * skrzepto (22) * stickster (19) * zodbot (7) * ryanlerch (0) * lmacken (0) * sayan (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Cheers, Justin W. Flory jflory7(a)gmail.com

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

fedora-join August 2016