Skip to content

Design docs file format changed from textfile to github md #1490

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

Closed

Conversation

domitian
Copy link
Contributor

@domitian domitian commented Feb 1, 2016

design.textile file in docs folder is now design.md with github flavoured markdown syntax. Also fixed some typos and grammatical mistakes in that file.

Typos fixed and changed to github flavoured markdown
@domitian
Copy link
Contributor Author

domitian commented Feb 1, 2016

Not able to add label to the pull request.

@bf4
Copy link
Member

bf4 commented Feb 1, 2016

Thanks for this @domitian

I'm not sure there's much value to changing it to md, since it's really just an archival doc, but since you did the work, I'll take a look at it.

Based on your comment in #1487 it looks like a useful change would be make it more clear this not the current design. The current design is the architecture doc.

@domitian
Copy link
Contributor Author

domitian commented Feb 2, 2016

@bf4 got your point, I changed the name of the doc to LEGACY-DESIGN.md which should make it clear that it is not current design doc.
Added to the start of this doc that this is not current design in bold case and to have a look at Architecture doc.

@bf4
Copy link
Member

bf4 commented Feb 2, 2016

Thinking about the file names .... Original_design and rename architecture to design? Initial_design?

@domitian
Copy link
Contributor Author

domitian commented Feb 2, 2016

yeah, for renaming architecture to design is good.
legacy_design if feel will give more meaning to the other doc than initial/original design, we could also think of old_design

@bf4
Copy link
Member

bf4 commented Feb 2, 2016

initial_? legacy and old don't really convey that it was the original design doc. Maybe in architecture just link to serializers.textile in Rails (before reverted) or README.textile in first 0.0.1 commit Or the DESIGN.textline form 0-8-stable or 0-9-stable? which was the source of this?

@bf4
Copy link
Member

bf4 commented Feb 2, 2016

while you're in here or in a new PR, we also need to change the yard docs links in the readme to http://www.rubydoc.info/github/rails-api/active_model_serializers/v0.10.0.rc4 since master doesn't appear to be updating.. and maybe also http://www.rubydoc.info/github/rails-api/active_model_serializers/0-9-stable and http://www.rubydoc.info/github/rails-api/active_model_serializers/0-8-stable

@domitian
Copy link
Contributor Author

domitian commented Feb 2, 2016

@bf4 created a new PR for the Yard docs links #1491

@domitian
Copy link
Contributor Author

domitian commented Feb 2, 2016

As per this commit from you in the past, the source is 0.8-stable.
I also did a manual diff to confirm it's source.
My suggestion is create a design folder and keep design documents for each version.

@bf4
Copy link
Member

bf4 commented Feb 3, 2016

Well, the doc was copied from there but it originated in rails before 0.0.1. The readme references the readme's of 0.8 and 0.9 which already serve the purpose of their design

B mobile phone

On Feb 2, 2016, at 11:43 AM, domitian [email protected] wrote:

As per this commit from you in the past, the source is 0.8-stable.
My suggestion is create a design folder and keep design documents for each version.


Reply to this email directly or view it on GitHub.

@domitian
Copy link
Contributor Author

domitian commented Feb 3, 2016

So should we just remove the file and add references in architecture doc about the past design?

@bf4
Copy link
Member

bf4 commented Feb 3, 2016

That's what I'm thinking now

B mobile phone

On Feb 2, 2016, at 9:35 PM, domitian [email protected] wrote:

So should we just remove the file and add references in architecture doc about the past design?


Reply to this email directly or view it on GitHub.

@domitian
Copy link
Contributor Author

domitian commented Feb 3, 2016

So should we link it and remove the file then?

@domitian
Copy link
Contributor Author

domitian commented Feb 4, 2016

Can I remove the file and add link in architecture.md then?

@bf4
Copy link
Member

bf4 commented Feb 15, 2016

Can I remove the file and add link in architecture.md then?

@domitian Yeah, that sounds good.

@bf4
Copy link
Member

bf4 commented Feb 26, 2016

@domitian Are you still interested in finishing this PR? #1490 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants