Git Product home page Git Product logo

Comments (7)

rwjblue avatar rwjblue commented on May 26, 2024 1

I agree, many of these notes have been cross linked (in various comments, blog posts, etc). I think it would be totally great to start using the correct terminology going forward, and we could even copy the contents into the correct place, but we shouldn't remove it from docs-team.

I think my concrete suggestion would be:

  • Add a top level learning-team folder
  • Start adding new content to learning-team
  • Add a docs-team/README.md explaining that the folder is legacy and new items are added in learning-team.
  • Optionally fail CI if a new file is added to docs-team (helps us to not forget 😛)
  • Optionally copy all existing docs-team content into the new folder

What say y'all?

from core-notes.

acorncom avatar acorncom commented on May 26, 2024

The context here is that the folder was named before the learning team became the learning team 😉 I have no objection in concept (it would be more consistent) but we’d also lose history in the process of the move. @locks can you explain your reaction here?

from core-notes.

mansona avatar mansona commented on May 26, 2024

@acorncom what would you mean by "los[ing] history" in this case? if we do it as a normal git move then the history will be maintained from a file perspective.

If we want to represent the fact that the docs team "evolved" into the learning team we should probably only move files after the date it was made official.

I just think it's odd that I'm adding something to the docs-team folder. I am not a member of the docs team, I'm a member of the learning team 😂 and it matters what you name things 👍

from core-notes.

locks avatar locks commented on May 26, 2024

My objection is a recurring one, I am not keen on breaking URLs for what I perceive to be little gain in this instance.

from core-notes.

rwjblue avatar rwjblue commented on May 26, 2024

Also, FWIW, learning-team was coined back in May of 2016, so at least some of the content here predates the newer term.

https://emberjs.com/blog/2016/05/19/introducing-subteams.html

We should decide if the content in the learning-team folder is just content after that date, or if it was "retroactive".

from core-notes.

amyrlam avatar amyrlam commented on May 26, 2024

Made this PR, please leave feedback, can make changes to get this closed! #273

from core-notes.

amyrlam avatar amyrlam commented on May 26, 2024

Closed via #273

from core-notes.

Related Issues (7)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.