search

pythonindia / inpycon2019

Website for PyCon India 2019
https://in.pycon.org
Other
16 stars 27 forks source link

Fix typos in Understanding Devsprints blog #197

Closed kurianbenoy closed 5 years ago

kurianbenoy commented 5 years ago

https://in.pycon.org/blog/2017/understanding-dev-sprints.html

astronomersiva commented 5 years ago

Hey @kurianbenoy, thanks for taking the time to report this issue.

I just took a look at the links and it seems like the blog post you are referring to is from the 2017 edition. That's the reason why the date shown is 2017 and tha's also why the CFP page is redirecting to the 2017 edition's proposals page.

PyCon India preserves blog posts every year and I don't think it's a good idea to update previous blog entries to point to the current edition's equivalents.

The text Deadline for submitting call for proposals is [Date]. is obviously wrong and can be changed. It would be great if you could do that in the blog repo. However, I am not sure what merits that would have considering that there will be almost no traffic to that page.

I am also curious as to how you ended up in such an old blog post so that we can try and ensure that all links point to the current edition only.

kurianbenoy commented 5 years ago

Hey @astronomersiva, I thought the blogpost is this year because seeing this year themed header in that page. I check that page: to see about what is devsprints for a similar event we are hosting in our college.

Do you have an updated blogpost for this year?

It may still be a good idea updating because on googling this blogpost may come on a casual search about Devsprints, as apparently this name is called only for Pycon India.

astronomersiva commented 5 years ago

https://in.pycon.org/blog/2019/understanding-devsprints.html - this is the blog post for this year's edition and I got this by Google Search only.

Like I said before, I don't think it is a good idea to replace dates in old blog posts. Not only is it wrong, there are clear indications of the post's authored date in page. I think that should serve as an indicator. There are also scaling issues. This is the 11th edition of PyCon India and even if there are 5 pages like these, whoever is organising this next year will have to update 5*11 + 5 = 60 pages. The year after that it will be 65 pages.

We can probably explore some other way of indicating that a post is outdated.