From Fedora Project Wiki
m (*agenda) |
(*agenda - next meeting) |
||
| Line 1: | Line 1: | ||
{{Template:DotNet_meeting2 | {{Template:DotNet_meeting2 | ||
|YEAR=2017 | |YEAR=2017 | ||
|MONTH= | |MONTH=08 | ||
|DAY= | |DAY=03 | ||
|HOUR=16 | |HOUR=16 | ||
|MINUTE=00 | |MINUTE=00 | ||
|CHANNEL=#fedora-meeting | |CHANNEL=#fedora-meeting | ||
|CHAIR=Rhea | |CHAIR=Rhea | ||
|agenda=* '''#startmeeting Fedora DotNet (2017- | |agenda=* '''#startmeeting Fedora DotNet (2017-08-03)''' | ||
* '''#meetingname dotnet''' | * '''#meetingname dotnet''' | ||
* '''#nick dotnet''' | * '''#nick dotnet''' | ||
| Line 28: | Line 28: | ||
* '''#topic Announcements''' | * '''#topic Announcements''' | ||
** #info === | ** #info === === | ||
*** #link | *** #link | ||
| Line 39: | Line 37: | ||
** #link https://pagure.io/fedora-dotnet/issues?tags=meeting | ** #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 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 === [WIP] developer.fedoraproject.org update #17 === | *** #info === [WIP] developer.fedoraproject.org update #17 === | ||
**** #link https://pagure.io/fedora-dotnet/issue/17 | **** #link https://pagure.io/fedora-dotnet/issue/17 | ||
| Line 46: | Line 45: | ||
*** #info === [INCOMPLETE] Rhea - create dev portal pages with example systemd service for ASP.NET Core, and example Apache/NGINX proxy configuration === | *** #info === [INCOMPLETE] Rhea - create dev portal pages with example systemd service for ASP.NET Core, and example Apache/NGINX proxy configuration === | ||
**** #action Rhea - create dev portal pages with example systemd service for ASP.NET Core, and example Apache/NGINX proxy configuration | **** #action Rhea - create dev portal pages with example systemd service for ASP.NET Core, and example Apache/NGINX proxy configuration | ||
*** #info === | --> | ||
*** #info === fedoraloves.net === | |||
**** #link https://pagure.io/design/issue/533 | |||
* '''#topic Packaging progress / Open Floor discussion''' | * '''#topic Packaging progress / Open Floor discussion''' | ||
* '''#endmeeting''' | |||
}} | }} | ||
Latest revision as of 15:16, 2 August 2017
Fedora DotNet Team Meeting Minutes 2017-08-03
Meeting Time
- 2017-08-03 16:00 UTC
- #fedora-meeting on freenode
Meeting Protocol
This week's DotNet Meeting will be led by Rhea.
- 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-08-03)
- #meetingname dotnet
- #nick dotnet
- #chair <given to approved members of FAS group at meeting>
- #topic Agenda
- #link https://fedoraproject.org/wiki/Meeting:DotNet_latest
- #info (1) Roll Call
- #info (2) Announcements
- #info (3) Action items and Tickets
- #info (4) Packaging progress / Open Floor discussion
- #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 Announcements
- #info === ===
- #link
- #info === ===
- #topic Action items and Tickets
- #link https://meetbot.fedoraproject.org/teams/dotnet
- #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 === fedoraloves.net ===
- #topic Packaging progress / Open Floor discussion
- #endmeeting