From Fedora Project Wiki

(+agenda)
 
m (*next meeting)
 
(3 intermediate revisions by the same user not shown)
Line 24: Line 24:
* '''#topic Roll Call'''
* '''#topic Roll Call'''
** #info Name; Timezone; Sub-projects/Interest Areas
** #info Name; Timezone; Sub-projects/Interest Areas
** #action dotnet New members, make sure you introduce yourself on the DotNet mailing list [ https://fedoraproject.org/wiki/DotNet ]
** #action dotnet New members, make sure you introduce yourself on the DotNet mailing list [ https://fedoraproject.org/wiki/SIGs/DotNet ]
** If this is your first time at a DotNet meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask.
** If this is your first time at a DotNet meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask.


Line 54: Line 54:
*** #info === [COMPLETE] Rhea Finalise the fas-group and pagure setup. ===
*** #info === [COMPLETE] Rhea Finalise the fas-group and pagure setup. ===
**** #info Kinda done there, except that we can't reaaally finish all that until we get nmilosev into the group, which would be done only when we submit package, so it's kinda weird.
**** #info Kinda done there, except that we can't reaaally finish all that until we get nmilosev into the group, which would be done only when we submit package, so it's kinda weird.
** #info === GSoC ===
*** #idea Do we want to mentor a Google Summer of Code project?
<!--
*** #info === Ticket #5 ===
*** #info === Ticket #5 ===
**** #info === "wiki/dotnet page" ===
**** #info === "wiki/dotnet page" ===
Line 59: Line 63:
**** #link https://fedoraproject.org/wiki/DotNet
**** #link https://fedoraproject.org/wiki/DotNet
**** #info vukovinski brought up this issue into foreground again, the wiki page is pretty much empty. We originally wanted this one to contain information about our packages, and useful references for dotnet itself. Any suggestions? Can we link to copr /nmilosev for F25 now or in near future when it's polished and we make sure that there are no issues?
**** #info vukovinski brought up this issue into foreground again, the wiki page is pretty much empty. We originally wanted this one to contain information about our packages, and useful references for dotnet itself. Any suggestions? Can we link to copr /nmilosev for F25 now or in near future when it's polished and we make sure that there are no issues?
 
-->


* '''#topic Packaging progress'''
* '''#topic Packaging progress'''
Line 67: Line 71:




|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2017-02-07/dotnet.2017-02-07-19.05.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting/2017-02-07/dotnet.2017-02-07-19.05.log.html
|next-meeting=2017-02-14
|next-meeting=2017-02-21
}}
}}

Latest revision as of 14:10, 21 February 2017

Fedora DotNet Team Meeting Minutes 2017-02-07

Meeting Time

Participants

This week's DotNet Meeting will be led by Rhea.

  • The participants will be posted after the meeting.

Meeting Protocol

  • To help improve the flow of the meeting, using the IRC Meeting Protocol is encouraged, as modeled by the EMEA Ambassadors.
  • Please follow the Meeting Protocol where possible.

Agenda

  • #startmeeting Fedora DotNet (2017-02-07)
  • #meetingname dotnet
  • #nick dotnet
  • #chair <given to approved members of FAS group at meeting>



  • #topic Roll Call
    • #info Name; Timezone; Sub-projects/Interest Areas
    • #action dotnet New members, make sure you introduce yourself on the DotNet mailing list [ https://fedoraproject.org/wiki/SIGs/DotNet ]
    • If this is your first time at a DotNet meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask.



  • #topic Action items and Tickets
    • #link https://meetbot.fedoraproject.org/teams/dotnet/dotnet.2017-01-17-19.04.html
    • #link https://pagure.io/fedora-dotnet/issues?tags=meeting
    • #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action it if needed. If no status, we'll try to get a quick update and move forward.
      • #info === [COMPLETE] Rhea Finalise the fas-group and pagure setup. ===
        • #info Kinda done there, except that we can't reaaally finish all that until we get nmilosev into the group, which would be done only when we submit package, so it's kinda weird.
    • #info === GSoC ===
      • #idea Do we want to mentor a Google Summer of Code project?


  • #topic Packaging progress


  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting