I think it does make sense to have it under the gluster organization. As for naming gluster-coreutils works as the intention is indeed to match the functionality of coreutils as much as possible. Craig > On Jun 14, 2015, at 2:29 AM, Niels de Vos <ndevos@xxxxxxxxxx> wrote: > >> On Fri, Jun 12, 2015 at 11:29:51AM -0700, chris holcombe wrote: >> Yeah I have this repo but it's basically empty: >> https://github.com/cholcombe973/GlusterUtils > > If you decide on a name, we can create a repository for you under the > https://github.com/gluster organization. That will make it easier for > others to find the repository and start contributuing or using it. > > Personally, I'd like a name like gluster-coreutils or something similar, > because I think the intention is to match the functionality and usage of > the standard coreutils as much as possible? > > Thanks, > Niels > >> >>> On 06/12/2015 11:27 AM, Craig Cabrey wrote: >>> Chris, >>> >>> That sounds good to me. >>> >>> I already have started on implementation, just to get familiar with the codebase and GFAPI. >>> >>> Is there a public repo that we can use for collaboration? >>> >>> Craig >>> >>>> On Jun 12, 2015, at 10:46 AM, chris holcombe <chris.holcombe@xxxxxxxxxxxxx> wrote: >>>> >>>> Craig, >>>> >>>> I was actually planning on building the same tool set. I would like to work with you also on this if that's ok. >>>> >>>> -Chris >>>> >>>> On 06/12/2015 10:43 AM, Jeff Darcy wrote: >>>>>> Hi everyone, >>>>>> >>>>>> This summer I am an intern at Facebook working on the Gluster team. Part of >>>>>> my project for the summer includes developing a set of coreutils that >>>>>> utilizes the Gluster C API natively. >>>>>> >>>>>> This project is similar in nature to the NFS coreutils that some of you may >>>>>> have heard about from the other Facebook engineers at the Gluster summit >>>>>> recently. I just wanted to reach out to the Gluster community to gather >>>>>> ideas, potential features, feedback, and direction. >>>>>> >>>>>> The initial set of utilities that I am developing includes the following: >>>>>> >>>>>> * cat >>>>>> * mkdir >>>>>> * put (read from stdin and write to a file) >>>>>> * mv >>>>>> * ls >>>>>> * rm >>>>>> * tail >>>>>> >>>>>> Again, any feedback will be welcome. >>>>> Hi, Craig, and welcome to the project. :) >>>>> >>>>> There seems to be some overlap with a proposal Ragahavendra Talur sent out >>>>> a couple of days ago. >>>>> >>>>> https://urldefense.proofpoint.com/v1/url?u=https://docs.google.com/document/d/1yuRLRbdccx_0V0UDAxqWbz4g983q5inuINHgM1YO040/edit?usp%3Dsharing&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=ThH6JMKaB%2Fxgkh9d2jPjehcdps8B69L0q04jdBbZvX4%3D%0A&m=86la5Xg7nlxAzIR6E5c2v2SgQSd6VssYzB%2BklM3wf%2BI%3D%0A&s=8d55bb5770b8ed1d683a6908a05af32b79289735c537c660252fcaa7c690e162 >>>>> >>>>> This seems like an excellent opportunity to collaborate. Ideally, I think >>>>> it would be useful to have both an FTP-client-like "shell" and a set of >>>>> standalone "one shot" commands, based on as much common code as possible. >>>>> >>>>> _______________________________________________ >>>>> Gluster-devel mailing list >>>>> Gluster-devel@xxxxxxxxxxx >>>>> https://urldefense.proofpoint.com/v1/url?u=http://www.gluster.org/mailman/listinfo/gluster-devel&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=ThH6JMKaB%2Fxgkh9d2jPjehcdps8B69L0q04jdBbZvX4%3D%0A&m=86la5Xg7nlxAzIR6E5c2v2SgQSd6VssYzB%2BklM3wf%2BI%3D%0A&s=28546cdc6fdf6f75f4cfa4b8260abc595eee96601a5f849ebb230ddbd1faf8b3 >> >> _______________________________________________ >> Gluster-devel mailing list >> Gluster-devel@xxxxxxxxxxx >> https://urldefense.proofpoint.com/v1/url?u=http://www.gluster.org/mailman/listinfo/gluster-devel&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=ThH6JMKaB%2Fxgkh9d2jPjehcdps8B69L0q04jdBbZvX4%3D%0A&m=yiRXm4P%2B7jkUD8T8QucHmE7RAd14NXpACGukNZ0KKRA%3D%0A&s=b0b8784ae9e5b4a6cc7cde03172898945f0e26a16ea086bc9ed3ca642162446f _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
