gistfile1.txt

[10:11:16] <nickvergessen> dachinat: You can see my work in https://github.com/nickv-nextcloud/nextcloudgo/blob/master/nextcloudgo.go
[10:11:17] <NextcloudBot> Title: nextcloudgo/nextcloudgo.go at master · nickv-nextcloud/nextcloudgo · GitHub (at github.com)
[10:11:23] <nickvergessen> but I didnt do a lot lately
[10:12:38] <dachinat> nickvergessen: I'll check that
[10:13:23] <nickvergessen> it only does status and capabilities atm I think
[10:13:39] <nickvergessen> the question is whether we should aline the methods
[10:13:58] <-- BubuIIC ([email protected]) hat das Netzwerk verlassen (Quit: Leaving.)
[10:17:05] <dachinat> I think it's good
[10:17:24] <dachinat> I don't know much about Go though
[10:18:41] --> rhabbachi ([email protected]) hat #nextcloud-dev betreten
[10:20:08] <nickvergessen> what I mean is the python thing is just a huge blob file with all methods
[10:20:20] <nickvergessen> and its not using anmespaces or something like that
[10:20:29] <nickvergessen> but I goes that might also be language dependent
[10:21:53] <dachinat> yeah I see
[10:22:51] <nickvergessen> for go lang its also easy to generate docs, because it automatically builds them from the method documentation of public methods
[10:23:02] <nickvergessen> so I guess as long as you write docs, this is all fine
[10:23:10] <nickvergessen> and doesnt over-complicate things
[10:26:37] <dachinat> I see, in ruby probably using yard as documentation tool pretty good results could be achieved by putting correctly formatted comments in code
[10:35:50] <dachinat> So, as for ruby api-wrapper name, as there's not only github repository name involved but rubygems.org from where package is fetched by other applications, I guess it'll need few adjustments.
[10:37:37] <dachinat> There's a small page about naming conventions http://guides.rubygems.org/name-your-gem/ msg me a suggestion about name later, if you'll have time
[10:37:39] <NextcloudBot> Title: Name your gem - RubyGems Guides (at guides.rubygems.org)
[10:47:50] --> BubuIIC ([email protected]) hat #nextcloud-dev betreten
[10:48:20] <nickvergessen> dachinat: I'd just use nextcloud if that works
[10:48:35] <nickvergessen> if not, append api or sdk
[10:52:10] <dachinat> okay if it's okay to have nextcloud as gem name, 'nextcloud' in require statement and Nextcloud as module I'll start preparing it
[10:56:18] <nickvergessen> I think so, but let me check back