On 19/06/2019 05:03, Stasiek Michalski wrote:
On wto, cze 18, 2019 at 2:19 PM, Imad Aldoj
wrote: Yeah I must agree, especially as Simon mentioned that the strategy at the time was aligned with the creation of the foundation but never came out so it seems like a perfect time to bring it to light again.
So apart from name and logo votes, we also will need surveys for contributors and users (two separate surveys that is), to see the target audience, the contributor goals, the userbase preferences etc etc. That would certainly help inform changes in websites, marketing, artwork, branding and other stuff that is user facing with distributions and beyond. I am hoping we would run those surveys for long enough, so we can also afford being very specific in the questions themselves, considering the recent contributions into more UX areas of mine as well as Kubic/containers/MicroOS experiences and goals (obviously not discarding older software/goals, but new areas weren't really commented nearly enough to get a feeling of how valuable they are overall to existing or emerging community). I guess it's more of my deep interest in community needs.
I would also be interested in multi-language answers, from communities outside of English speakers, just to see how the overview of community engagement and support looks from country to country, from language to language. If anybody is willing to help with translations there, it would be pretty cool, suggesting questions is also valuable, because I am not aware of everything that happens within the community, so your input is important!
There are voices from within the user base that marketing for sysadmins ignores the longstanding commitment of openSUSE to desktop, which is pretty fair, considering the technologies within the openSUSE have been focused around simplifying typically cli/config-editing work into something easily understandable by grandparents ;D
I like this idea, particularly in the context of working out what our website content (tying into the other thread) and marketing should look like and target. There is certainly plenty of scope for improvement in these areas. At the same time I think this can and should be done independently of the foundation discussion, the main reason for this is that with the type of foundation we are looking to setup the goal / charter that is set for the foundation can never be changed. As such whatever it is needs to be broad enough to cover everything the project is doing now and may want to do into the future or alternatively it needs to be a very vague limited statement that leaves the project lots of room to move in many directions. Currently the board has been working from the latter, and the current version that we will put for discussion on this list very soon looks something like this. "The openSUSE Foundation is a not for profit organisation that believes in empowering its Contributors so that the user community can benefit from the best, most-sustainable and most-innovative open source software. To achieve this, most of the daily work is performed by the Foundation's Contributors. Nonetheless, certain bodies or committees will be in charge of work when the decision-taking requires extraordinary decisions, litigation, conflict resolution, funding, treasury, strategic technical decisions, strategic technical guidance, and general guidance on orientations. In principle, the processes, discussions and decisions of openSUSE Foundation, of its Committees, of its Board and of its Officers are public, and decisions are taken in a rational and transparent manner." If you think that can be improved lets discuss that in the Foundation thread when it appears likely very soon. As far as a vision strategy for the next few years this is much harder, as there is no one in the project who can tell anyone else what they should or shouldn't work on beyond rules and guidelines that teams have created to make there life simpler, think packaging guidelines, guidelines on what should go onto each mailing list etc. As such I don't think surveying contributors then merging there results together to create a strategy is the best idea, instead we could just ask all our contributors / teams what there goals visions and strategy is for the future and collate them into one place. But even then we are a project of many many different facets and products and the strategy for some things may completely contradict others so i'm not sure doing this on a project wide scale makes huge sense, for example the openqa, obs and yast teams may have completely different visions for what they want to do into the future. Looking at the distro's we intentionally have 2 very different distro's with very different aims goals and users as such as a developer my plans for tumbleweed into the future are completely different to my plans for leap. So i'm not sure if this idea would lead to something meaningful if we tried to do it project wide. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org