+100 for starting this SIG. We already have a special mailing list for UX, 
and starting a SIG would be a great opportunity to discuss the UX/UI topics 
and to create a joint vision for it inside the project

We'll be using Zoom to host the meetings and record them 
> https://cloudbees.zoom.us/j/621503564.


Why don't we use the CDF Zoom account instead? Using other Zoom account 
creates a bus factor for the SIGs.

BR, Oleg 

On Monday, November 18, 2019 at 12:29:19 PM UTC+1, Jeremy Hartley wrote:
>
> In keeping with JEP-4 <https://github.com/jenkinsci/jep/tree/master/jep/4>, 
> I'm posting to the developer mailing list my plan to create and lead the 
> Jenkins User Experience  special interest group.
>
> I'll submit a pull request to jenkins.io with the structure described in 
> JEP-4 <https://github.com/jenkinsci/jep/tree/master/jep/4>.
>
> The first UX special interest group meeting is scheduled for Tuesday, 
> November 26th, 2019 at 16:00 UTC. The proposed meeting agenda is at 
> <https://docs.google.com/document/d/1uNNo0QJKPHnNp8PGr_jLI8p3K_94ZYD-M0evZOEZ93c/edit#>
> https://docs.google.com/document/d/1xA6UN7ORv3OFYBC3Kw6y4mtqDekAjwYVNhsrH4PBwBk/edit?usp=sharing
>  
> . We'll be using Zoom to host the meetings and record them 
> https://cloudbees.zoom.us/j/621503564. The videos will be published to 
> YouTube.
>
> *Draft mission statement*:
>
> The User Experience SIG focuses on improving Jenkins user interface and 
> user experience. The SIG will seek feedback from the community on the 
> current UI and UX and new designs proposed by SIG members and others and 
> will discuss alternatives, identify compromises, and test implementations 
> to improve the Jenkins UI / UX.
>
> Thanks,
>
> Jeremy Hartley
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/33b06a72-c505-4df8-be35-3ccc3cdc68ef%40googlegroups.com.

Reply via email to