Hey there!😉
We are excited to announce that the “Community Terms” necessary for preparing to welcome collaborators to the bitBuyer Project have been finalized!

This post is meant to serve as a storage for the terms, so I’ll keep the chatter to a minimum.

Below are the terms.
Cheers!🎉

This English version is provided as a reference translation. We strive to ensure that it remains faithful to the original Japanese version. However, in case of any discrepancies, the official and legally binding version is the Japanese version.

Additionally, the translation accuracy has been verified by ChatGPT-o1, an advanced reasoning model from OpenAI.

Article 1 [Purpose]

This community aims to support the development and operation of the OSS (Open Source Software) project bitBuyer Project, and to promote technical exchanges.

Article 2 [Source Code Rights and Licensing]

1. The copyright of source code contributed to the bitBuyer Project belongs to the respective authors.
2. However, contributed source code will be released under the GPLv3 license, allowing reuse, modification, and redistribution.
3. Copyright attribution will be explicitly recorded and managed by listing credits within bitBuyer.py (Monolithic), ensuring all contributors are properly acknowledged.
4. Use of External Libraries & Frameworks
   • The use of libraries and frameworks compatible with GPLv3 is assumed.
   • If the license compatibility is unclear during implementation, please consult the administrator (Shohei KIMURA).
5. Security of Third-party Code
   • External libraries and contributed code will undergo a vulnerability check to the maximum feasible extent before release.
   • If you discover any suspicious code or security risks, please report them immediately to the administrator (Shohei KIMURA).
   • Security Reporting Contact
     • Reports should be sent via email to bitbuyer.0.8.1.a@icloud.com.
     • The subject should be “Security Report”, and the details of the discovered vulnerability, along with the reproduction steps, should be included as thoroughly as possible.
     • The administrator (Shohei KIMURA) will review the report and take necessary actions.
   • As bitBuyer Project is an OSS, it is difficult to completely eliminate security risks. Please use the software at your own discretion.

Article 3 [Coding Rules]

1. Coding rules should follow those specified at the beginning of bitBuyer.py.
2. Within that framework, the rules will conform to PEP8, but strict adherence is not mandatory.
3. For questions regarding coding rules, please consult via Discord Support Lounge.
4. Changes to coding rules should be avoided where possible.

Article 4 [Communication and Code of Conduct]

1. Operational Rules for Communication Tools
   • Discord Support Lounge: Primarily used for technical discussions, code reviews, and support.
   • LINE Open Chat: Primarily used for gathering opinions on project direction and conducting majority votes, as Discord does not provide a built-in voting feature.
   • Since Discord does not have a built-in voting feature, important decisions requiring a vote will be conducted via LINE Open Chat.
2. Respectful Communication & Language Etiquette
   • All discussions should be conducted in a respectful and professional manner. Excessively informal language should be avoided.
   • Respect the opinions of other members and strive for constructive discussions.
   • Personal attacks, harassment, and discriminatory remarks are prohibited.
3. Encouragement of Open Discussion
   • All technical discussions should take place in the Discord Support Lounge.
   • For decision-making in the bitBuyer Project, opinion gathering and voting (majority rule) will be conducted in LINE Open Chat.
   • All major decisions will be published on the official website.

Article 5 [Contribution Guidelines]

• Since the bitBuyer Project follows a monolithic structure (single file), code merging is done manually by the administrator (Shohei KIMURA).
• Code proposals should follow these steps:
  1. Create a separate file documenting the proposed changes (not bitBuyer.py).
  2. Name the file descriptively, such as “ChangeDescription_Date.txt”.
  3. Upload the file to Discord Support Lounge and explain the changes.
  4. The administrator (Shohei KIMURA) will review and manually integrate the changes into bitBuyer.py.
• Direct modifications to the GitHub repository are not permitted.
• Pull requests can be submitted, but since merging is done manually by the administrator (Shohei KIMURA) to maintain consistency and project stability, they will not be directly merged on GitHub.

Article 6 [Project Management and Decision-making]

1. The administrator of the bitBuyer Project, Shohei KIMURA, holds the final decision-making authority and bears the ultimate responsibility for all decisions.
2. As the project expands, the administrator (Shohei KIMURA) may appoint moderators as deemed appropriate.
3. Roles of Moderators
   • Maintain community order and facilitate discussions.
   • Issue warnings or notices in case of policy violations.
   • Manage Discord Support Lounge and LINE Open Chat operations.
   • Moderators may express their opinions on significant decisions but do not have decision-making authority.
4. Conflict Resolution Among Moderators
   • If conflicts arise, the administrator (Shohei KIMURA) will review both perspectives and make the final decision in alignment with the bitBuyer Project’s operational philosophy.
   • Public discussions can be held for conflicting opinions, but final authority remains with administrator (Shohei KIMURA).
5. Moderator Appointment & Dismissal
   • Moderators are appointed and dismissed at the discretion of the administrator (Shohei KIMURA).
   • If a moderator fails to fulfill their duties or takes actions significantly deviating from the project’s policies, the administrator (Shohei KIMURA) may remove them.
   • Reappointment requires approval from the administrator (Shohei KIMURA).

Article 7 [Prohibited Actions]

1. License Violations
   • The use of external code that does not comply with the GPLv3 license is strictly prohibited.
2. Spam & Advertisements
   • Unrelated advertisements and commercial activities are prohibited.
3. Speech that is disrespectful or irrational is not allowed
   • Speech that may cause undue stress or harm to other members is prohibited.
4. Disruptive or Offensive Behavior
   • Slander, abusive language, and harassment are strictly forbidden.
5. Illegal Activities
   • Actions that undermine the bitBuyer Project’s integrity, such as financial fraud or money laundering, are prohibited.

Article 8 [Handling of Violations]

1. Moderators can issue warnings in case of community terms violations.
2. In cases of serious violations or repeated disruptive behavior, the administrator (Shohei KIMURA) may take action to enforce removal from the community.
3. The administrator (Shohei KIMURA) holds the final decision-making authority regarding removal from the community.

Article 9 [Disclaimer on Financial Transactions]

1. bitBuyer Project involves cryptocurrency and financial transactions.
2. All transactions using the bitBuyer Project are carried out at the user’s sole risk.
3. Neither the administrator (Shohei KIMURA) nor the developers take any responsibility for profits or losses.

Article 10 [General Disclaimer]

1. The software and information provided by bitBuyer Project are distributed “as is”, with no guarantees.
2. The administrator (Shohei KIMURA) and developers are not responsible for any damages resulting from its use.

Article 11 [Information Management and Privacy]

1. Public Availability of Discord Support Lounge and LINE Open Chat Logs
   • Statements and discussions in the Discord Support Lounge will generally be made public.
   • The results of votes and key discussion points in LINE Open Chat may also be published on the official website as needed.
2. Handling of Personal Information
   • The posting of personal information is not recommended. Please be particularly cautious about disclosing email addresses, real names, or other sensitive details.
3. Credit Attribution Policy
   • The legal names of copyright holders will be used for credit attribution in the source code.
   • Only the administrator (Shohei KIMURA) will have access to the real name-to-alias mapping, and it will not be disclosed to third parties under any circumstances.
   • Real name submissions are conducted via direct email communication with the administrator (Shohei KIMURA).
4. Applying for Credit Under a Handle (Pseudonym)
   • We generally recommend using your real name for credit.
   • However, if there are specific legal or safety concerns, contributors may apply for credit under a pseudonym. Applications will be accepted only in the following cases:
     1. If revealing the real name poses a concrete legal or personal safety risk, such as stalking, threats, or social persecution.
     2. If the laws of the contributor’s country explicitly prohibit or create significant disadvantages for real-name disclosure.
     3. Other exceptional cases at the sole discretion of the administrator (Shohei KIMURA).
   • Application Process for Handle-Based Credit
     1. Submit an email request to the administrator (Shohei KIMURA) with the subject: “Application for Handle-Based Credit”.
     2. Provide a clear and concise explanation of why an exception is needed.
     3. The administrator (Shohei KIMURA) will review the request and notify the applicant of approval or rejection.
     4. If approved, the requested handle will be formally registered for credit notation.
   • Handles must be appropriate and professional; offensive or excessively informal names will not be accepted.
   • The application details will remain strictly confidential and will not be disclosed to third parties.
   • If a handle is used for credit, claiming rights without explicit proof of identity may become difficult in the future.

Article 12 [Legal Compliance]

1. Members of the bitBuyer Community should comply with with the laws of their respective jurisdictions.
2. If the community’s activities face potential legal issues, seeking expert legal advice is recommended.
3. The bitBuyer Project does not condone illegal activities. If any unlawful actions are identified, the administrator (Shohei KIMURA) reserves the right to take necessary actions.

Article 13 [Donations and Sponsorship]

1. Donation Management and Usage
   • Until the bitBuyer Fund is established, the administrator (Shohei KIMURA) will be responsible for managing donations.
   • Donations will be utilized to support the maintenance, growth, and development of the bitBuyer Project.
   • Donations will be utilized to support both project development and financial stability, with transparent reporting on investment usage. Any fees incurred during investment operations will be covered within the allocated donation funds.
   • If the bitBuyer Fund is established, the remaining balance will be transferred to the fund within the limits of the original donation amount.
   • The use of donations is strictly limited to the following purposes.
     1. Payment of bounties (performance-based rewards) for high-difficulty development tasks.
     2. Allocation of funds for the technical infrastructure necessary to maintain and operate the bitBuyer Project, including domain renewal fees, official website hosting costs, and SEO optimization expenses.
     3. Expenses for promoting and raising awareness of the bitBuyer Project, including documentation creation and the development of educational support content.
   • The use of donation funds will be disclosed on the official website as appropriate.
2. Sponsorship Policy
   • The bitBuyer Project maintains neutrality and will not be influenced by sponsors.
   • Sponsors cannot influence the decision-making or technical direction of the project.
   • Sponsor names and logos may be displayed on the official website at the discretion of the administrator (Shohei KIMURA).
3. Donation and Sponsorship Procedures
   • Donations will be accepted via methods designated by the administrator (Shohei KIMURA) (e.g., PayPal, bank transfer).
   • Until the bitBuyer Fund is established, donations will be personally managed by the administrator (Shohei KIMURA), but balance changes will be disclosed on the official website.
   • To apply for sponsorship, please contact the administrator (Shohei KIMURA) via email (bitbuyer.0.8.1.a@icloud.com).
   • If a donation or sponsorship agreement is finalized, the details will be published on the official website.

Article 14 [Amendments to the Community Terms]

1. These terms may be updated as the bitBuyer Project grows and technology evolves.
2. Any revisions will be announced on the official website or through various communication channels.

Article 15 [Community Expansion and Operational Adjustments]

1. Operational Policies for Expansion
   • As the bitBuyer Project and its community grow, operational policies and management strategies will be regularly reviewed and adjusted as needed.
   • Any new or modified rules will be published on the official website and communicated to the community.
   • Before implementing new rules, community feedback will be gathered via LINE Open Chat, and adjustments will be made as necessary.
2. Expansion of Moderator Roles
   • As the community expands, moderator roles and responsibilities will be reviewed.
   • If necessary, roles may be subdivided into positions such as Technical Support, Community Management, and Donation Management Assistance.
   • The selection criteria for moderators will be adjusted based on community size, and transparent appointment processes will be established.
3. Donation and Fund Management in Large-Scale Operations
   • If donations increase significantly, the management system will be reviewed, and an audit process may be introduced.
   • If the bitBuyer Fund is established, clear governance and fund management policies will be implemented.
   • To ensure transparency, regular financial reports may be published on the official website.
4. Policy for Organizational Restructuring
   • If the community grows to a scale where the current management structure is insufficient, alternative governance models (e.g., transitioning to a non-profit organization) may be considered.
   • Before making such major changes, community discussions and agreements will be conducted.
5. New and Modified Supplementary Rules
   • Any new supplementary rules will be published on the official website and shared via Discord Support Lounge and LINE Open Chat.
   • All rules will be formulated in accordance with bitBuyer Project’s operational philosophy and OSS licensing principles.

Article 16 [Multilingual Support]

1. Priority of Terms Language
   • The official version of these terms shall be the Japanese version, while the English version is provided as a reference translation.
   • In the event of any discrepancies between the Japanese and English versions, the Japanese version shall take precedence.
   • The English version is a reference translation, and in case of any interpretational differences, the Japanese version shall always take precedence, and all clarifications must be based on the Japanese text.
2. Translation Policy
   • The English version of the terms will be updated periodically using ChatGPT-assisted translation.
   • The community may provide feedback to improve translation accuracy.
3. Contributions from Non-Japanese Speakers
   • Contributions from English-speaking developers will be accommodated as much as possible.
   • English technical documentation may be created to support non-Japanese contributors.
   • While the official community platforms (Discord Support Lounge & LINE Open Chat) will primarily use Japanese, English communication will be supported as needed.

Article 17 [Project Dissolution and Administrator Succession]

1. Dissolution of the bitBuyer Project
   • If the bitBuyer Project is no longer sustainable, a formal dissolution announcement will be made via the official website and community channels.
   • In such a case, all source code and related documents will remain publicly available under the GPLv3 license.
   • The management of project infrastructure (bitbuyer.dev domain, servers, etc.) will be decided at the discretion of the administrator (Shohei KIMURA).
2. Administrator Succession
   • If the administrator (Shohei KIMURA) of the bitBuyer Project becomes unable to continue managing the project, administrative authority will be transferred in accordance with the internal agreement stated at the beginning of bitBuyer.py, as agreed upon between the stakeholders and the administrator (Shohei KIMURA).
   • This internal agreement is documented in writing, signed by hand, scanned, and managed as a PDF file, which is exchanged via email.
   • In the event of an administrative transfer, the new administrator shall uphold the principles of the bitBuyer Project and respect its OSS license, ensuring the continued operation of the project.
3. If the transfer of administrative authority does not take place
   • If no suitable successor exists, the bitBuyer Project will be dissolved, and the source code will be archived as open source.
   • Regarding the continuation of the community, discussions will be held with moderators and relevant members, and a new structure may be established if necessary.

Article 18 [Requests from Public Institutions]

1. Basic Policy on Requests from Public Institutions
   • The bitBuyer Project complies with applicable laws and will respond appropriately to requests from government agencies, financial regulatory authorities, and law enforcement organizations.
   • However, if a request conflicts with the neutrality of the bitBuyer Project or the principles of the OSS license, appropriate legal counsel will be sought before making a decision.
2. Policy on Information Disclosure
   • If the administrator (Shohei KIMURA) receives a formal request from a public institution, the legitimacy of the request will be verified before disclosing any information.
   • The information subject to disclosure will be limited to data related to the bitBuyer Project, such as logs from the Discord Support Lounge and LINE Open Chat, publicly available information on GitHub, and content from the official website.
   • To protect user privacy, the scope of disclosed information will be kept to a minimum, and unnecessary personal data will not be provided.
3. Procedure for Handling Disclosure Requests
   • If the administrator (Shohei KIMURA) receives an information disclosure request from a public institution, the following steps will be strictly followed to ensure legal compliance and user privacy protection:
     1. Verify the legitimacy and legal basis of the request (ensure it is a formal written request).
     2. Obtain legal advice if necessary.
     3. Carefully assess the scope of disclosure and minimize the information provided.
     4. Notify affected users if legally permissible.
     5. Provide the required information through appropriate channels in compliance with regulations.
4. Ensuring Transparency
   • If a disclosure request is made by a public authority, the summary of the request will be published on the official website to ensure transparency, unless prohibited by law.
   • We will consider publishing the number of disclosure requests and their response status in an annual report.