-
Notifications
You must be signed in to change notification settings - Fork 700
Conversation
add utf-8 header(example)
# -*- coding: utf-8 -*- setup.py pcl_visualization comment off
(HarrisKeypoint3D headerfilename changing by pclversion pcl-1.6 : harris_keypoint3D.h pcl 1.7 : harris_3d.h)
1.7/1.8)
This reverts commit e4d2dfe.
Hi @Sirokujira, that's a terrific extension, also in terms of all newly wrapped modules! It seems to me that this original project is dormant/abandoned, do you perhaps want to open your repository for full use as a successor (I think your fork is the most advanced one), e.g. allowing to post issues to your code? Because I just found one: In |
Whether you are going to create an original project However, if you create a project as original In addition, it is necessary to think about the module name. |
Or perhaps you could write to [email protected] so that they add you as project-owner? |
@strawlab @astraw @hdorothea Could you consider allowing @Sirokujira to become a maintainer of this repository? It seems like he has been doing a good job maintaining it over the last couple of years. https://github.com/Sirokujira/python-pcl/tree/1.7_to_1.9 @Sirokujira If you don't hear from the authors, might I suggest taking the approach taken by https://github.com/python-pillow/Pillow/ in a similar situation (details) where they created a new repository with a new name. It is possible that the pcl authors would allow you to create it on their organization page https://github.com/PointCloudLibrary. The license is consistent so that aspect should be good to go. If making a permanent fork please consider initializing a new repository so it is searchable because forks are not searchable. |
@ahundt Thanks for the mention -- not sure why, but I wasn't getting notified on this. I just sent an invite to @Sirokujira to join the repo. @Sirokujira you are welcome to merge as you see fit, release updates under the current name and to update the master branch. @nzjrs I presume you are OK with all this. I don't see any commits from you since February 2016. |
@astraw I'd like to confirm, but can I use an external test CI (Appveyor / Travis CI) for the current repository? If you do not have a test environment, I would like to ask for cooperation with the above test environment. |
@Sirokujira OK to use external test CI - let me know if I need to do anything to set it up, but you should be able to. |
Regarding Travis CI, It seems that there is synchronization between accounts Could you just check whether strawlab / python-pcl is checked? Regarding AppVeyor, Go to https://ci.appveyor.com and add an account. With the current Appveyor account |
Regarding Travis CI: there is https://travis-ci.org/Sirokujira/python-pcl and https://travis-ci.org/strawlab/python-pcl . The strawlab version is for this repository. I just created https://ci.appveyor.com/project/astraw/python-pcl . Please let me know if this works and if you need more. |
@astraw |
Cool! Perhaps it might make sense to tag a release as well? |
Build support in Windows environment
Reference example of official website Partial implementation
Adding automatic test configuration file