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

Add isavasyopanishad (madhyandina) #17

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

epicfaace
Copy link
Contributor

Add isavasyopanishad (madhyandina recension). This comes as an export from Ambuda's proofing for this text -- https://ambuda.org/proofing/isavasyopanishad-text-only/

@akprasad regarding folder structure -- I just made a folder called "other_texts" where we can begin storing the texts we create using Proofing. Eventually we could then rename this repository to texts and then potentially reorganize the folders further?

Copy link
Contributor

@akprasad akprasad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay here -- I was thinking through where I want these texts, but I still don't have a great answer. I'm a little more cavalier with code, but I want to think through how we store this data and represent its lineage, not only within the document but also within the repo.

In particular, I want to think through the case where we have a text in the repo that someone requests we remove. Do we just strip that text from the repo and rewrite history? Or perhaps we could have multiple repos based on the text source or license guarantees.

I'm likely overthinking this, but I'd rather overthink our approach here and get the approach right than pick something reasonable and have to shuffle texts around. I'm curious what you think as well.

other_texts/sa_IzAvasyopaniSad-mAdhyandina.xml Outdated Show resolved Hide resolved
@epicfaace
Copy link
Contributor Author

@akprasad I think that if someone requests we remove a text, and we decide to do so, it should be fine to rewrite history. I'd imagine this may not be a routine occurrence -- it would occur rarely enough that rewriting history should be OK. it's also worth reading GitHub's DMCA takedown policy, particularly the section around forks.

I think multiple repos would get logistically pretty complicated to handle, but we might want to revisit that question once we get a large enough volume of content contributed to Ambuda.

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

Successfully merging this pull request may close these issues.

2 participants