Setup projects

[acid-chicken]

Overview

This project is divided by information network services.

Namespaces

The following are the divided projects.

Syntax

Project Namespace Branch

Description

Information.NET.Common Information common

Common interfaces goes here.

Information.NET.Services.Frost Information.Services.Frost service/frost

Implementation of Information.NET.Common's interfaces for Frost.

Information.NET.Services.GnuSocial Information.Services.GnuSocial service/gnu-social

Implementation of Information.NET.Common's interfaces for GNU social.

Information.NET.Services.Mastodon Information.Services.Mastodon service/mastodon

Implementation of Information.NET.Common's interfaces for Mastodon.

Information.NET.Services.Misskey Information.Services.Misskey service/misskey

Implementation of Information.NET.Common's interfaces for Misskey.

Information.NET.Services.Twitter Information.Services.Twitter service/twitter

Implementation of Information.NET.Common's interfaces for Twitter.

Information.NET.Services.Yanaka19 Information.Services.Yanaka19 service/yanaka19

Implementation of Information.NET.Common's interfaces for Yanaka19.

[marihachi]

what's members in Information.NET.Common?

[acid-chicken]

@marihachi We're gonna have a discussion about that, so I'll submit a new issue for talking about it.

[marihachi]

Information.NET.Commonに定義されたインターフェイスを各サービスが実装しようとすると、それぞれのサービスのブランチでInformation.NET.Commonのプロジェクトを参照しないといけないと思うんだけど、どうするつもりなんだろう

When each service tries to implement the interface defined in Information.NET.Common, I think that it is necessary to refer to the project of Information.NET.Common in the branch of each service, but what will you do?

[marihachi]

commonブランチをすべてのサービスブランチがマージするという方法が考えられる

There is a way that all of the service branches merge common branch. — Translation added by @acid-chicken

[acid-chicken]

@marihachi Of course, all of the service branches are referencing the common project. The common branch is merged into master when the developing has been finished ordinary. After merging, we can implement the common interfaces.

[marihachi]

でも、後になってcommonに変更が生じたときはそのcommonの変更をmasterブランチに再度マージして、masterブランチを全てのサービスブランチにマージする必要があるよね？

However, We have to re-merge common branch to master branch when there happen changes in common branch, and after that, we also need to merge master branch to all of the service branches. — Translation added by @acid-chicken

[acid-chicken]

@marihachi Yes. Therefore we develop the common interfaces studiously.

[marihachi]

ok

[marihachi]

プロジェクト全般的に言えることだけど、対象フレームワークはどうしますか

In all of the projects, which target framework are you going to choose? — Translation added by @acid-chicken

[acid-chicken]

@marihachi I'm planning to use .NET Standard 2.0.