Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2016 year in review #159

Closed
iteles opened this issue Jan 2, 2017 · 6 comments
Closed

2016 year in review #159

iteles opened this issue Jan 2, 2017 · 6 comments
Assignees
Labels
enhancement New feature or enhancement of existing functionality priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished

Comments

@iteles
Copy link
Member

iteles commented Jan 2, 2017

I'm pretty terrible at these, but we should write one and share it widely.

We've achieved so much and it would be great for dwylers to realise just what was done, despite the year ahead being so awesome.

Mostly, doing this soon will make sure I actually write things down as they're happening in 2017*.

@iteles iteles added enhancement New feature or enhancement of existing functionality question A question needs to be answered before progress can be made on this issue labels Jan 2, 2017
@nelsonic
Copy link
Member

nelsonic commented Jan 3, 2017

@iteles totally agree that you are the best person to write this "post".
I just reviewed a few PRs and wrote a few "readmes" ... you did everything else...! ❤️ ✅
Maybe you can note down the outline/bullet-points in the car on Wednesday...?
If you need anything from me, please let me know!

@ghost ghost assigned iteles Feb 25, 2017
@ghost ghost added the priority-1 Highest priority issue. This is costing us money every minute that passes. label Feb 25, 2017
@iteles iteles added priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished and removed priority-1 Highest priority issue. This is costing us money every minute that passes. labels Mar 13, 2017
@iteles
Copy link
Member Author

iteles commented Mar 13, 2017

Pulling down the priority on this, whilst it is important and does have a ticking clock, it is not 'urgent' and can become a Year in Review based on our financials as well.

Part of this will be captured next week in preparation for #213

@iteles iteles removed the question A question needs to be answered before progress can be made on this issue label Mar 13, 2017
@nelsonic
Copy link
Member

removing the priority, might as well change the year on it to 2017... cause the next time you will have time to reminisce about the past will be in the "Christmas Holidays" (i.e. December 2017).
🎄 🎅 🎁

@ghost
Copy link

ghost commented Mar 14, 2017

Agreed that this needs to be done in preparation for #213 anyway

@Cleop
Copy link
Member

Cleop commented Oct 26, 2017

Was this issue achived for #213 or is this something we should be preparing for Dec 2017 as @nelsonic mentioned?

@ghost
Copy link

ghost commented Oct 26, 2017

@Cleop this was never written up, but I've now moved them to the blog repo:
dwyl/blog#22
dwyl/blog#23

@ghost ghost closed this as completed Oct 26, 2017
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or enhancement of existing functionality priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished
Projects
None yet
Development

No branches or pull requests

3 participants